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]
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
256.372.7102 (Telephone)
256.372.4961 (Facsimile)
[log in to unmask] (Electronic
Mail)
http://www.aamu.edu (Website)
“Service is Sovereignty”
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.