1 / 45

資訊組織研究 : 全集資料描述標準 Collection Level Description (CLD)

資訊組織研究 : 全集資料描述標準 Collection Level Description (CLD). 張迺貞. Incident Archived in 3 Different Subject Collections. Air crash Cargo plane 28 Republic of Congo. 依 Metadata 屬性 / 特質區分. 來源 internal ( 如 file names and header information) vs.

livi
Download Presentation

資訊組織研究 : 全集資料描述標準 Collection Level Description (CLD)

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 Description (CLD) 張迺貞

  2. Incident Archived in 3 Different Subject Collections • Air crash • Cargo plane 28 • Republic of Congo Naicheng Chang

  3. 依Metadata屬性/特質區分 • 來源 internal (如file names and header information) vs. external (如cataloging recs, legal information) • 產生方式 automatic vs. manual • 性質 creator vs. expert • 狀態 static vs. dynamic; long-term vs. short-term • 結構 structured vs. unstructured • 語意 controlled vs. uncontrolled • 層次 collection vs. item (Gilliland-Swetland, 2000) Naicheng Chang

  4. What is a collection?(Dunsire, 2003) • “Any aggregation of individual items (objects, resources)” • CD Focus briefing paper 1 • Size is not a factor – 1 item is possible • Varying degrees of permanence • Physical juxtaposition not necessary; collections can be distributed across multiple locations • Cross-domain • Libraries, museums, art galleries, archives etc. • “Useful” defined in terms of “Functional granularity” Naicheng Chang

  5. What is CLD? • Collection-Level Description • Metadata at the level of aggregation: Title:William Speirs Bruce Collection Description:Collection of material on oceanography and Arctic and Antarctic exploration, bequeathed by Dr. William Speirs Bruce, Polar explorer and oceanographer (1867-1921). Location: Edinburgh University Library. Main Library Collectors:William S. (William Speirs) Bruce (1867-1921) [Collecting: Closed] Subjects: Antarctica--Discovery and exploration Part of: Edinburgh University Library. Department of Special Collections printed books collections Naicheng Chang

  6. What is a collection?(Chapman, 2006) • A group of resources with a common factor • On the same topic • In the same format • Belong(ed) to a person or organisation • For a specific group of people Naicheng Chang

  7. Size doesn’t matter • Bath University Library – 440,000 volumes • Harborow Collection – 5 left-hand gloves • Victoria Art Gallery – 150 china dogs • Bath Chronicle – 100 linear feet of stored photographs • No.1 Royal Crescent – a house • Public Record Office – 69 royal charters, commissions and mandates • Royal United Hospital – 1,000 e-journals Naicheng Chang

  8. Why collection description? • Enable collection provider to • disclose information about collections to users • Enable user to • discover/locate collections • select collections to explore/search on basis of summary description • compare collections as broadly similar objects (even where items are heterogeneous) • understand conditions of access and use • interpret collections Naicheng Chang

  9. What is collection-level description? • CLD schema = sets of data elements about: • The collection • Agents connected with the collection • Location of the collection • Associated resources • Relationships of the above entities • Implementations • Usually hold descriptions in a relational database • Have a specific focus • May extend or limit the metadata elements used Naicheng Chang

  10. Collection ofmetadata records Collection of physicalobjects Collection of books Collection of digitalitems Database of CLDs CLDs provide high-level “map” of landscape for user, researcher, visitor…. (Chapman, 2006) Naicheng Chang

  11. Confusing Terms • Collection-Level Description • The complete metadata for a collection • The process of creating a CLD • Collection-Description • A finding-aid for the collection (e.g. catalogue) • Description • An attribute of a Collection giving a short summary of the collection history and contents, etc. Naicheng Chang

  12. Why is CLD important? (1) • Ideally, all metadata/retrieval is at the level of the work (item-level description) • But in the Real world … • Online ILD metadata not available • Legacy; Institutional policies • Wide variation in ILD structure and content standards • Between domains; within domains • Within single institutions! Naicheng Chang

  13. Why is CLD important? (2) • CLD offers broader coverage • More stuff can be found • Cheaper to implement • High recall, low precision • Some metadata cannot be accommodated in ILD without extensive duplication • E.g. Collection title, Collector, Owner, Location, etc. Naicheng Chang

  14. Why is CLD important? (3) • Collaborative management • Collaborative acquisition policies • Preservation and storage • Priorities for digitisation, wider access, etc. • Landscaping in distributed digital information environments • Portals • Broad overview, then more precise discovery Naicheng Chang

  15. Landscaping Search term or Profile parameter e.g. name, subject, education level, accessibility Retrieve relevant CLDs to create broad "map" of concentrations of resources: peaks of significance; "lodes" for further exploration CLDs link to digital collections, and online (analytic) finding aids Local ILDs for resource discovery: cross-searching possible with Z39.50/OAI Naicheng Chang

  16. Development of CLD in UK • Entity-relationship model • Michael Heaney • Also covers analytic finding aids: collection-descriptions (C-Ds) • Database schema • For RSLP by UKOLN; simplifies Heaney’s model • Implementation • JISC IE Services Registry; simplifies RSLP Naicheng Chang

  17. Heaney’s Analytic Model Naicheng Chang

  18. SCONE Story (1)(ScottishCOllections NEtwork, Dunsire, 2003) • SCONE project • Collaborative collection management • HE/FE plus public libraries sector (SEED) • CDLR as lead site • Test datasets • SLIR; SWOP; ESH; Websites • Then Heaney's model and RSLP schema • SCONE service • 2600 CLDs Naicheng Chang

  19. SCONE Story (2) • SQL database (MS SQL Server) • Uses Heaney’s analysis rather than RSLP • Fully relational, normal form • Incorporates additional metadata not specified • Subject strengths (RCO) • Service-level description elements (CAIRNS) • ColdFusion Web data server • DreamWeaver Website maintenance Naicheng Chang

  20. SCONE Story (3) • CC-interop (COPAC/Clumps interoperability) project • Cross-relates SCONE to major UK schemas • SCONE clone for RIDING clump • HaIRST (institutional resources) and SPEIR (Scottish portals) projects • SCONE used for landscaping Naicheng Chang

  21. JISC Information Environment • “the set of network or online services that support publishing and use of information and learning resources” • Functional model for resource discovery has 4 stages • Observes that some components already exist or are under development Naicheng Chang

  22. JISC IE Functional Model • 1: Enter • Initial landscape: presentation of collections & services for local service or user profile • 2: Survey • Modify set of collections & services • 3: Discover • Item-level searching using distributed (z39.50) or physical (OAI harvested; FTP) union catalogue • 4: Detail • Further information about items Naicheng Chang

  23. IE for Scotland (A) Entry Initial landscape [Scottish Cultural Portal; SCONE] Survey Collection descriptions service [SCONE] Landscaper Collection-level descriptions Naicheng Chang

  24. IE for Scotland (B) Discover Distributed union catalogue [CAIRNS] Harvested union catalogue [HaIRST] Union catalogue [COPAC] Detail Item metadata Item metadata Item metadata Item metadata Naicheng Chang

  25. Tap into Bath Using RSLP CD Schema(Chapman, 2006) • Cross-domain, cross-sectoral collaboration • Staff development • Opportunities to network • Practical experience of: • Creating the database • Collecting (& entering) data • Differences in domain approaches • Open source software for re-use (Southern Cross) Naicheng Chang

  26. Aims and objectives • Introduce concept of collection description to information professionals in Bath • Produce a comprehensive resource for Bath • Pilot project for local collection description databases using open source software • Support re-use through documentation Naicheng Chang

  27. Tap into Bath Partners • Libraries: 2 university, 1 college, 1 school, 1 hospital trust, 1 utility company, 1 newspaper • Archives: Bath Abbey, public Record Office, 1 university, 1 charities archive • Museums: 13 – various, including a house • Art gallery: 1 public gallery Naicheng Chang

  28. Tap into Bath Collections • Varying sizes • Wide range of resource formats • Some have item level catalogues • Some of which are online • Publicly funded & commercial Naicheng Chang

  29. Issues: Data Content • Text length in <Description> • Advised 1 short paragraph • Range of data in <Access Conditions> • Opening hours • Admission charges or free entry (omitted actual charges) • Accessibility • Other features – guided tours, packs for schools • Creator / Owner / Administrator • Partners sometimes unclear on distinction Naicheng Chang

  30. Issues: Element Labels • Making field labels user friendly, e.g. • Object = Star item • Physical characteristics = Materials held • Accumulation date range = When collected • Contents date range = Age of materials • Sub-collection = Contains • Super-collection = Part of • Accrual status = Collecting policy • Access control = Who can use it? • Access conditions = Access information Naicheng Chang

  31. Issues: Technical & Maintenance • Finding a server • Charges? Willing to host long-term? Server configured in a standard way? • Launch December 2004 - Now: team contacts partners and then does update • Future: potential to develop password protected interface for partners Naicheng Chang

  32. Issues: Granularity • Schema supports hierarchical records • Establishing which collections needed separate records • Public library – 29 collections • Roman Baths Museum – 5 collections • Items can be in 1+ collections • Maps – local history, map, reference Naicheng Chang

  33. Issues: Indexing • Which terminology to use? • None ideal – LCSH best fit • Possible move to UKAT(UK Archival Thesaurus) • Partners suggested terms • Team identified LCSH form of term • Time periods - problematic Naicheng Chang

  34. Collection level description: Ongoing projects at the University of Illinois at Urbana-Champaign and Digital Library Federation(Shreeves and Foulonneau, 2005) The CIC metadata portal http://cicharvest.grainger.uiuc.edu Naicheng Chang

  35. IMLS Digital Collection Registry • Funded by Institute of Museum and Library Services (IMLS), a federal agency, to centralize access to the digital collections created through grant projects funded by the IMLS by the: • Creation of a database of these digital collections • Harvesting item level metadata from these collections into an aggregation via the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) Naicheng Chang

  36. http://imlsdcc.grainger.uiuc.edu/collections/ Naicheng Chang

  37. Collection-enabled Functions • Co-locating resources • Grouping results • Browsing collections • Filtering results • Selecting relevant search results • Interpret item description • Search granularity • Search collections only • Search items with collection information Naicheng Chang

  38. Adding Context Naicheng Chang

  39. Filtering / Selecting Naicheng Chang

  40. Searching / selecting source / co-locating Naicheng Chang

  41. Suggesting complementary resources Naicheng Chang

  42. Harvest set descriptions DC Coll. records Collections.xml MARC records Creation of CLD for the CIC metadata portal Item database merge SQL db enrich DLXS Grab thumbshots of collection homepages Naicheng Chang

  43. Issues Raised in DLF-NSDL Best Practices for OAI http://oai-best.comm.nsdl.org/cgi-bin/wiki.pl?TableOfContents • Collection description useful for providing context to item level metadata • Issue: How to best share collection descriptions using OAI? • Issue: Distinguishing between descriptions of a collection of resources and the OAI set description Naicheng Chang

  44. Where? • As a separate record in an OAI set or repository along side the item level metadata and referenced in a relation field in the item level metadata – generally not liked by service providers • As a separate record in an OAI set devoted only to collection descriptions. The collection description could be located by a GetRecord link in the set description. • A link to a collection description on a web page. This could be embedded in the set description and/or the item level metadata records; or • In the set or repository description…. Naicheng Chang

  45. OAI sets as collections of metadata records • How many records • Metadata formats • Documentation of metadata practice • Relation to other sets • When last updated • What does the metadata describe • Collection level description Naicheng Chang

More Related