1 / 10

DC-Library Working Group

DC-Library Working Group . DC-8 Ottawa, Canada 5 October 2000. Agenda. Review of charge What are libraries doing with DC? Current projects Impediments to using DC What would libraries like to do with DC? Library application profile. Charge .

nani
Download Presentation

DC-Library Working Group

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. DC-Library Working Group DC-8 Ottawa, Canada 5 October 2000

  2. Agenda • Review of charge • What are libraries doing with DC? • Current projects • Impediments to using DC • What would libraries like to do with DC? • Library application profile

  3. Charge • Foster interoperability between DC and library metadata • Articulate library concerns • Keep library community informed • Consider reasons to experiment more widely in libraries • Build library implementors community • Register library specific elements/qualif.

  4. Library uses of DC • Dublin Core serves internationally as an interchange format between various systems; supports reusability • Harvesting metadata from databases within and outside of library systems • Create library catalog records for Web resources within local ILS or within CORC • Expose MARC data to other communities through DC • Get data from other non-library creators

  5. Impediments to use of DC in libraries • Inability to input records in library ILS • Inability to use records in local ILS • Link to authorities • Used more for specific projects • Reluctancy to create simple records • How to get further use in libraries

  6. Library adaptation of DC • Application profiles • what would a library one look like? • Additional elements and qualifiers • Audience • Holdings • Access and Use • Distinction and use of relation and source • Compile list of relation qualifiers of use to library community

  7. Library application profile • Changes to semantics • Required elements • Title • Identifier • Identifier of object itself; what if not electronic? • Content rules • When does element become part of DC elements when many communities use it?

  8. Deliverables • Analyze qualifiers • Recommend best practices • Collect examples of DC use in libraries • Identify, evaluated, share existing DC use and documentation • Provide input in development and maintenance of crosswalks

  9. Deliverables • Share existing data with DC registry (e.g. encoding schemes such as LCSH, authority files, other standards) • Investigate how to provide URI transparency to library database resources (e.g. authority records) • Develop library application profile • Consult with IFLA WG on metadata • Consider documentation on DC in MARC (template, manual) for library ILS use (application profile with additional guidance)

  10. Deliverables • Share existing data with DC registry (e.g. encoding schemes such as LCSH, authority files, other standards) • Investigate how to provide URI transparency to library database resources (e.g. authority records) • Develop library application profile • Consult with IFLA WG on metadata • Consider documentation on DC in MARC (template, manual) for library ILS use (application profile with additional guidance)

More Related