1. MarLIN: a research data metadatabase for CSIRO Marine Research Tony Rees Divisional Data Centre CSIRO Marine Research, Hobart e-mail contact: Tony.Rees@marine.csiro.au

2. Role of a Metadatabase To hold metadata corresponding to Divisional research data holdings in the most effective manner for subsequent searching, retrieval, and export/metadata exchange metadata = structured summary information about datasets - e.g. dataset name and description, coverage in space and time, completeness, access, keywords, contributor or project names, etc. etc. (10-200 possible fields) metadatabase should permit searching by spatial or time periods, subject matter, keywords, free text, etc. may also contain ancillary information such as links to references, www documents, project details, etc.

3. Division of Marine Research’s particular needs DATA DOCUMENTATION Determine and catalogue what data the Division holds, in what form, and where located - for both current and historic data DATA SUPPLY Provide an interface for particular users to link to on- line datasets, to facilitate self-service retrieval of data and associated documentation METADATA EXPORT Supply metadata for appropriate Divisional datasets to external metadata directories, e.g. the “Blue Pages” Marine & Coastal Metadata Directory

4. Desired metadatabase model Format Dataset descriptions to be held in an Oracle relational database, for ease of maintenance and efficiency of storage, with a WWW interface for data entry and retrieval Administration Divisional staff to be able to contribute (and if necessary, update) metadata entries to the database, moderated by a database administrator Searching Users to be able to search by geographic criteria, time period, subject category, keywords, or free text in title and other fields

5. “Green Pages” software (basis for MarLIN) Oracle relational database, with WWW screens constructed using HTML and Oracle Web Agent (OWA) Software developed by Computer Power P/L for Environment Australia Contains much of the initial functionality and metadata fields envisaged for use in “MarLIN” Anticipated changes… – 10-15 additional fields, for CMR-specific needs – Some redesign of search and data entry interfaces – Customisation/ development of various picklists, maps, graphics, etc. – New modules to hold project and research voyage details, species names and codes – New database access constraints (read/write privileges etc.) – Other modifications as needed for improved functionality and correct operation of the database

6. “Green Pages” basic search screen

7. “Green Pages” JAVA search screen

8. MarLIN keywords SUBJECT CATEGORIES and KEYWORDS ANZLIC “Search Words” replaced by more detailed MarLIN subject categories (based on existing ASFA subject categories in series 1000’s, 200’s and 4000’s) Categories are grouped into 8 major “subject areas” for higher level searching Keywords are coded hierarchically - searching on a “parent” will automatically look for any “children” (each keyword is assigned a type, a level, and a parent) Other keyword types include habitat, taxonomic group, equipment used, parameters measured, etc…

9. MarLIN keywords - screen example

10. Generalised search flow (original)

11. Generalised search flow (new)