Next Meeting: 3D Metadata

Join us at the next Metadata Discussion Group meeting for a discussion of 3D metadata! This will not be covering metadata in the actual third dimension but rather metadata needed to describe, discover, and access 3D digitized objects online. Indiana University is involved in several projects working with digital objects in 3D, including IUPUI’s digital library work in 3D digitizing (3D Scanning for Small Budgets: How Local Libraries and Museums Will Play a Role in Creating a 3D Digital Library), the Virtual World Heritage Library, and the Center for Biological Research Collections. Join us as we explore what questions to ask, what metadata we need, and how best to provide that metadata for 3D discovery and access.

DATE: Tuesday, November 29
TIME: 9-10am
PLACE: Wells Library Room 043
TOPIC: 3D Metadata
MODERATOR: Julie Hardesty

Next meeting: Paths to a Linked Data Catalog

Join the next Metadata Discussion Group meeting, where we’ll welcoming in the new academic year with a discussion about the many possible paths to implementing linked library data. Participants will consider homegrown and vended solutions and think about the implications of when and where to introduce linked data into library data stream.

DATE: Tuesday, September 20
TIME: 9-10 am
PLACE: Wells Library Room 043
TOPIC: Paths to a Linked Data Catalog
MODERATOR: Jennifer Liss

We hope to see you there!

Save the Dates: Fall 2016 meetings

The Metadata Discussion Group at Indiana University Libraries welcomes anyone from the IU community to attend our upcoming meetings.

Meetings will be from 9:00 am – 10:00 am in Room 043 of the Wells Library.

September 20
Paths to a Linked Data Catalog
Moderator: Jennifer Liss

November 29
TBD
Moderator: Julie Hardesty

Hello from Summertime!

Just a quick note to our Metadata Discussion Group blog readers to let you know that we might be quiet right now but we are still discussing metadata!

Jennifer and I are both still involved in the MODS and RDF Descriptive Metadata Subgroup within the Hydra community. We’ll likely have additional decisions from that group regarding mapping MODS to RDF and some demo tools to share this fall.

If you have a metadata topic you are interested in discussing, please suggest a topic and if you’re not on our email list make sure you’re on that so you stay updated.

Thank you for your attention and please continue enjoying your summer!

Moving from MODS to usable RDF

[UPDATE: This meeting IS happening and is now scheduled for Tuesday, April 5 from 9-10am in Wells Library 043. Apologies for missing the meeting where this was originally scheduled but this thing is BACK ON! And don’t forget to check out Jennifer’s post discussing More about MODS (and XML) to learn more about MODS and its uses before we meet.]

It’s been a while since the Metadata Discussion Group last met but Jennifer and I think we have something that could benefit from a few more metadata-aware eyes at IU. If that’s you, or if you’re interested in topics like transforming metadata or linked library data, read on!

There is an ongoing effort in the Hydra community to figure out strategies to deal with descriptive metadata in RDF for use in Fedora 4 (the digital object repository that we hope to upgrade to here at IUB Libraries). The MODS and RDF Descriptive Metadata Subgroup, lead by Steven Anderson from the Boston Public Library, is working on how to handle MODS XML as RDF that will create a usable, if unofficial, metadata application profile to bring MODS into Fedora 4 as RDF properties.

So far this work has involved going through MODS element by element using examples from various institutions and asking the question “If [you] had to move that [MODS element] to RDF in Fedora 4 today, what would [you] chose to do with it?” (see the work for Abstract as an example). The MODS elements examined so far include name, title, typeOfResource, genre, originInfo, physicalDescription, abstract, language, and current work is happening on tableOfContents.

Join us on Tuesday, April 5 from 9-10am in Wells Library 043 to learn about this effort and Indiana University Libraries’ participation. We’ll share contributed examples and discuss how the MDG might help this effort along for IU and the Hydra community.

Round Robin Updates – March 2016 meeting summary

The discussion on Moving from MODS to usable RDF, originally planned for March 8, will be rescheduled (date TBD). Stay tuned!

Since the time was blocked off on everyone’s calendars (and since we hadn’t met in a while), group members participated in a round robin. Below is a summary of the updates. Errors and misunderstandings on my part may be corrected in the comments below and I’ll do my best to update the post.

ORCHiD

  • Andrea Morrison reported seeing more and more ORCiD identifiers in Library of Congress Name Authority File (NAF) records

Browse Functionality in Progress for IUCAT

  • Rachael Cohen reported on the progress to implement browse for IUCAT
    • Working from code developed by Cornell (they also use Blacklight for their discovery layer)
    • Development team will start with author browse, then tackle Kinsey subject headings, then Library of Congress Subject Headings (LCSH)
  • Spencer Anspach clarified how browse will work:
    • Authorized access points in bibliographical records will be hyperlinked
    • Browse results will display all access points (authorized and unauthorized) that appear in bibliographic records–all results will have a number next to it, denoting how many times that access point is used in the bibliographic records database; some access points will have an icon next to them, which will denote that the access point is the authorized version (NAF, etc.)
      • Clicking on the icon will take a user to the authority record for that authorized access point (MARC 670 fields will NOT display to users)
    • Clicking on any of the access points will conduct a search on that access point
  • Concerns: batch loaded records from vendors (we won’t mention names) do not have authority control; one vendor in particular never includes dates (MARC subfield d) in authorized access points–this will certainly have an adverse impact on browse!
  • Shelf ready materials often do not have authority control–those errors are picked up in post-cataloging, by the Database Management team

Use of BoundingBox Tool Adds Value to Map Records

  • Heiko Mühr reported a pilot (and subsequent adoption) of the BoundingBox Tool
    • The tool allows catalogers to find geographical coordinates for an area and outputs longitude and latitude data in a number of formats (including–but not limited to!–OCLC MARC)
    • After piloting use of the tool in the month of December, catalogers determined that use of the tool did not adversely impact cataloging productivity–the quality of records increased
    • Coordinate data is now required in bibliographic records for sheet maps

Government Publications Metadata Update

  • Andrea Morrison reported on her collaboration with the new GIMMS librarian
    • Working on finding ways to streamline acquisitions and cataloging workflows and provide better metadata services for federal documents

Media Digitization and Preservation Initiative

  • Ronda Sewald reported on progress made in the Media Digitization and Preservation Initiative (MDPI) project
    • Tens of thousands of media objects have been digitized to date
    • Digitization is ongoing
    • Currently sorting out ways to determine the rights for digital objects and how to create metadata (at such a huge scale) for discovery

Medical Subject Headings (MeSH) Deconstruction Update

  • James Castrataro reported that the deconstruction of MeSH headings seems to be complete
    • It was uncertain whether or not MeSH access points could by subdivided chronologically before the December 2015 decision to deconstruct
    • No one present was sure whether or not MeSH access points can be subdivided chronologically at present

Using the Catalog to Support Teaching

  • Bob Noel sought recommendations from the group for providing access to individual vendor streaming video titles (records were batch loaded at the item-level, rather than the collection-level)
    • Participants came up with a handful of possible strategies including, creating a LibGuide where all updates to links, etc., would be handled in one place
    • Interesting discussion about making access as easy as possible for the user (faculty, researchers, and students)