1 / 12

Collection Level Data Problems

Collection Level Data Problems. … & Suggestions for Avoiding Them. “Metadata” Sources. BioCase data is provided by NNs all over Europe. NNs use different styles to enter data in their collection level database (Nodit etc.)

ssasaki
Télécharger la présentation

Collection Level Data Problems

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. Collection Level Data Problems … & Suggestions for Avoiding Them

  2. “Metadata” Sources • BioCase data is provided by NNs all over Europe. • NNs use different styles to enter data in their collection level database (Nodit etc.) • How can we preserve the clarity and uniformity of data so that users can easily locate the information they are searching for?

  3. Data Structure • Capture the hierarchical structure of your organizations and collections. • Enter organization information in the database (Nodit etc.), and then enter the collections that belong to it. • For every organization, specify its type and the number of collections it contains.

  4. Data Structure II • Do not enter “orphan” collections. “Orphan” collections are collections that are not connected to an organization parent. • Unsure how to classify an organization? Nodit has a list of organization classes!

  5. Data Structure III • The Nodit list includes “independent expert”, “voluntary observer”, and “other” so you can even create organizations for collections that belong to individuals. • There is no need to ever enter standalone collections.

  6. Collection Organization XXX Herbarium XXX Herbarium Collection Data Structure IV • Even if an organization only contains a single collection, enter them as 2 separate records. • Add the word “collection” to collection names if not already there. Ex – “algae collection” rather than simply “algae”.

  7. Free Text Fields • Use English wherever possible in addition to other languages. • Avoid notes that the indexing tool cannot decipher. “For details see URL”, “data still incomplete ”, “unknown”. • Keep data in their proper fields. Town: “Jerusalem 92542” Town: “Jerusalem”; Zip: “92542”

  8. Keywords • Longer free text descriptions such as a collection’s description, access restrictions, and purpose are helpful to users viewing full result sets. • However, searches use keywords to locate results. • Use keywords correctly so that searches locate your collections!

  9. Keyword Tips • Keep keywords content-specific. “All” for taxon, geographic, timeperiod “world” or “worldwide” for geographic • Sometimes you may want to add some keywords to help a collection be located. “Kenya”… && … “Africa” “musci”… && … “plantae”

  10. Keywords Tips II • Only use a single term for each keyword. Do not combine entries with “and” or “,”. “Butterflies and moths” “fungi, lichens, algae”  Enter a separate keyword for each word.

  11. Keywords Tips III • Using dates for time-period keywords: “last 300 years” or “18th century” or “about 1900”  Use: “1975” “1700-1800” “1975+” “2000-” • If you are unsure of the exact year then estimate a brief interval.

  12. Data Quality Reporting • A automatic mechanism for reporting data quality problems to NNs is being developed.

More Related