LISTSERV 16.0 - MODS Archives

Agreed Melissa,

We use different subject heading lists depending on the collection. We actually pay quite a bit of attention to our thesis collections because the content is so specific. That’s where the new knowledge comes from. BUT because we can search full text versions of the newer pdf versions (our IR converts the text in a pdf into a plain text document for searching) that helps, but how that moves to linked data in the future I cant tell you. Most of our collection now has the plain text version for searching, and the older scanned documents we paid a bit more attention to.

We do the metadata in an xml editor, then upload the xml editor into the database with the object.  We have also started using VIAF for URI’s, but I am still testing including the |0 for the viaf URI in our opac records.

As for learning as we go, and OH BOY have we learnt plenty over the last few months – we only started using genre about 16 months ago and it’s still a clean-up process for our cataloguers to work through, but I think we would manage to do that with some kind of a global update process. We also make sure that our Leader and 00X’s are 100% accurate in the OPAC as it affects searching, facets etc. more than anything else.

I have created templates for each material type (if that makes sense) with what we consider the bare minimum (or RDA speak CORE) elements required for the repository, because MODS is so ‘compatible’ with MARC21 it’s the easiest to convert and we already understand MARC. We also make 100% sure that each object in the IR at least have a description (abstract).

Each template is different, for thesis we have all the basics and subjects, I try and add at least one verified subject from http://id.loc.gov/ even if it is very broad or basic, just to give it SOMETHING… the rest… I wing.

I did however see an image just two days ago of a subject that was a combo with the separate entities that are sub dividable with UIR’s (I hope you can see it here). What this does or how it will work I cant tell you yet… Ignore the 2x 655’s I am doing a test with this record…

[cid:[log in to unmask]]

What worries me is the need for us to make global changes to our collections and some tools seem to be better designed for this than others…

My problem is that the URI rules we apply to our OPAC must also apply to our IR and open journal publishing format, the subject headings need to come from the same place and all the names for persons must be verified if we want true linked data to apply in future. So the rules should probably maybe perhaps apply to all kinds of bibliographic records no matter where they might be.

Regards,
Suzanne Saunders

From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Melissa Burel
Sent: Friday, 02 November 2018 15:53
To: [log in to unmask]
Subject: [Newsletter] Re: [MODS] URI Automation

Hi Suzanne,

Maybe this isn’t the best answer, but so far URI inclusion for me has been dependent on the collection itself. Some of them have common subject headings that we can include URIs for and some do not. None of the names for our theses are established, so I’ve can’t include those URIs. Also I’m finding it depends on workflows (the theses workflow is very different from scanned items from the archives). So for some of our metadata, I follow an excel spreadsheet, to OpenRefine, to a MODs template workflow. If the metadata has similar fields (all in English, the 100 is the “author”, etc.) I’m finding that I can include URIs by incorporating them into the MODs template. Then it’s there for every record and I don’t have to include it in the spreadsheet or add it in by hand later. In this workflow I’ve been adding the URIs for name and subject in the Excel, however there is still hand editing that has to happen to delete null values. I don’t know if there is a best practice recommendation somewhere about this. I definitely want the name, subjects, and genre, but then beyond that it just depends. But you’re right, it is good to document the decisions made in terms of URIs. I have been including that in the documentation for each collection, but I still struggle with what’s “good enough.” Also I’m learning as I go, so what I know now makes me want to redo every previous collection for little things that could be better (of course I don’t, because who has the time for that?)

Melissa


From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Saunders, Suzanne (Ms) (Summerstrand Campus North)
Sent: Friday, November 2, 2018 8:37 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [MODS] URI Automation

Hi Melissa,

That is just the problem, we don’t know if it’s working yet. We have been harvesting our database to google scholar, but we haven’t really tested. So I can’t answer that at all…

With deciding which elements/fields to give URI’s I think we look at what the field represents, the sky is indeed the limit I guess. What we do is document what we decide, and I personally focus on the elements that can provide links to enhance discovery and not format (as much) but I haven’t got any answers, the example I sent is purely experimental.

I have an idea that whatever we do now might have be adjusted/updated/changed in the future simply because we don’t know what the future holds…

Letting go is a problem, where do you stop??

Regards,
Suzanne Saunders

From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Melissa Burel
Sent: Friday, 02 November 2018 15:30
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: [Newsletter] Re: [MODS] URI Automation

Hi Suzanna,

Thank you for sharing this! How do you know if your linked data is really linking and doing what it’s supposed to do? Is there a place one can check?  Also from what I’m reading it seems like almost every field could have linked data (language, genre, names, relators, etc.) how do you decide which linked data to include? Personally I can’t keep production going at an amount that satisfies my administration AND include every possible linked data field, but I’m having a hard time letting things go.

Melissa

From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Saunders, Suzanne (Ms) (Summerstrand Campus North)
Sent: Friday, November 2, 2018 12:59 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [MODS] URI Automation

Hello Melissa,

We have been playing with the idea indeed, but we have no idea if it works as it should…

We have been doing this as a test. Some of these take the ‘possibilities’ to the extreme, but we wanted to know what’s possible and what works.  We do this type of enhancement manually as xml mods files an upload them, so there is no workflow at all… it’s a bit mad at the moment.


<genre authority="mrcgt" authorityURI="https://www.loc.gov/standards/valuelist/marcgt.html" valueURI="https://www.loc.gov/standards/valuelist/marcgt.html">thesis</genre>

  <language>
    <languageTerm authority="ISO 639-2b" authorityURI="http://id.loc.gov/vocabulary/languages/eng" type="code">eng</languageTerm>
   <languageTerm type="text">English</languageTerm>
  </language>

  <subject authority="lcsh" authorityURI="http://id.loc.gov/authorities/subjects">
    <topic valueURI="http://id.loc.gov/authorities/subjects/sh93004310">Bible -- Feminist criticism</topic>
  </subject>

  <subject authority="lcsh" authorityURI="http://id.loc.gov/authorities/subjects">
    <topic valueURI="http://id.loc.gov/authorities/subjects/sh85013617">Bible -- Criticism, interpretation, etc.</topic>
  </subject>

  <subject authority="lcsh" authorityURI="http://id.loc.gov/authorities/subjects">
    <topic valueURI="http://id.loc.gov/authorities/subjects/sh89004268">Postmodernism -- Religious aspects</topic>
  </subject>

And where we find data:

  <name type="personal">
    <role>
      <roleTerm type="code">ths</roleTerm>
      <roleTerm type="text">Thesis Advisor</roleTerm>
    </role>
    <namePart>Naidu, Sam</namePart>
  </name>

  <name type="corporate" authorityURI="http://id.loc.gov/authorities/names" valueURI="http://id.loc.gov/authorities/names/n80050412">
    <role>
      <roleTerm authority="marcrelator" type="text">Degree granting institution</roleTerm>
      <roleTerm authority="marcrelator" type="code">dgg</roleTerm>
    </role>
    <namePart>Rhodes University</namePart>
    <affiliation>Faculty of Humanities, English Language and Linguistics</affiliation>
  </name>

  <name type="corporate" authorityURI="http://id.loc.gov/authorities/names" valueURI="http://id.loc.gov/authorities/names/no00086694">
    <role>
      <roleTerm authority="marcrelator" type="text">Degree funder</roleTerm>
      <roleTerm authority="marcrelator" type="code">fnd</roleTerm>
    </role>
    <namePart>National Research Foundation (South Africa)</namePart>
  </name>

<name type="personal" authority="orcid" authorityURI="http://id.loc.gov/vocabulary/identifiers/orcid.html" valueURI="http://orcid.org/xxxx-xxxxxxxx-xxxx">
<role>
                                <roleTerm type="code">aut</roleTerm>
                                <roleTerm type="text">Author</roleTerm>
                </role>
<namePart>Surname, Name - one for each creator</namePart>
  <affiliation>University of Port Elizabeth</affiliation>
  <description>Department at the time</description>
  <description>SARChI Chair</description>
  <description>Distinguished Professors</description>
  <description>Top 30 Rhodes Researchers (2016)</description>
</name>


Regards,
Suzanne Saunders

From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Melissa Burel
Sent: Thursday, 01 November 2018 16:23
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: [Newsletter] [MODS] URI Automation

Hi there,

Has anyone heard of or practice the automation of adding URIs to MODS records? I’m aware of ways that it can be incorporated when converting spreadsheet data to MODS, but was wondering if anyone had a different workflow for adding the identifiers?

Sincerely,
Melissa


Melissa Burel, MLIS, MM
Metadata Cataloging Librarian
J.F. Drake Learning Resources Center
Alabama A&M University
Normal, AL 35762<https://maps.google.com/?q=4900+Meridian+Street+%0D+Normal,+AL+35762&entry=gmail&source=g>
256.372.7102 (Telephone)
256.372.4961 (Facsimile)
[log in to unmask]<mailto:[log in to unmask]> (Electronic Mail)
http://www.aamu.edu<http://www.aamu.edu/> (Website)
“Service is Sovereignty”


 [cid:[log in to unmask]]



CONFIDENTIALITY NOTICE:
This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication may contain protected confidential information, health information, financial services information, or proprietary information. If you are not the intended recipient or the individual responsible for delivering the email to the recipient, please be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this e-mail in error, please advise by return e-mail and permanently delete this e-mail from your computer system.


________________________________

NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard Nelson Mandela University eMail disclaimer which may be found at:
http://www.mandela.ac.za/disclaimer/email.htm

________________________________

NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard Nelson Mandela University eMail disclaimer which may be found at:
http://www.mandela.ac.za/disclaimer/email.htm

________________________________

NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard Nelson Mandela University eMail disclaimer which may be found at:
http://www.mandela.ac.za/disclaimer/email.htm