1 / 6

(Version 3.0, July 2002)

(Version 3.0, July 2002). www.chesapeakebay.net/comet. Quick Review. Why COMET... Needed to develop a formal, user-friendly process for entering and editing CIMS/FGDC compliant metadata records AND

esben
Download Presentation

(Version 3.0, July 2002)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. (Version 3.0, July 2002) www.chesapeakebay.net/comet

  2. Quick Review Why COMET... • Needed to develop a formal, user-friendly process for entering and editing CIMS/FGDC compliant metadata records AND • Address the issues of metadata management, long term metadata storage, and dynamic search & retrieval. • The available stand-alone tools did not address these critical management issues.

  3. Quick Review COMET was developed as a Cold Fusion-based online tool for metadata creation • Users can create and edit CIMS / FGDC compliant metadata via standard browser • Records added directly to the CIMS Metadata Database and CIMS FGDC node • Version 1 allowed users to document simple, CIMS level 1 data - May, 1999 • Version 2 allowed users to document all 3 levels of CIMS data, included help files and an import and export tool for compliant FGDC text - January 2000

  4. Version 3 • July 1st, 2002 • Database migrated to SQL Server and 100% of FGDC and NBII fields were included in the new, fully relational design • FGDC standard adhered to more strictly • Further simplified record entry process, especially for level one metadata (e.g. fact sheets) • Design revamped, less cluttered, single column • Help files improved, easier to access and read

  5. Tasks Ahead • Train and educate user community • Facilitate metadata entry • Move towards Project based inventory with highly cross-referenced records • Add additional fields to interface as necessary • Discontinue support of import routines • Use XML format for output • Improve searching

  6. DATA COMET FGDC Compliant text records FGDC Clearinghouse CIMS Metadata Database XML Output CIMS Clearinghouse Node CIMS Metadata Search Clearinghouse Metadata Searches Metadata and data

More Related