Melanie Wacker | 22 Oct 23:11 2014

MODS/XML to BIBFRAME

Hello all,

In response to the many calls for a MODS to BIBFRAME mapping in the last few months the MODS Editorial Committee has developed a MODS to BIBFRAME mapping table. Based on this, Stanford is working on an XSLT to convert MODS/XML to BIBFRAME. We will share the result as soon as it becomes available with this list.

In the meantime, we have also heard of some other institutions and individuals working on their own MODS to BIBFRAME transformations. We (and probably many others on this list) are very interested in learning more about these initiatives. So if you are working on something that you are willing to talk about, please post it to this list or feel free to contact a member of the MODS EC directly.

Regards,
Melanie

on behalf of the MODS Editorial Committee

Myung-Ja Han | 3 Oct 21:36 2014

Job Posting: E-Serials Bibliographic Control Specialist, University of Illinois at Urbana-Champaign

E-Serials Bibliographic Control Specialist (Academic Professional)

University Library

University of Illinois Urbana Champaign

 

Position Available: As soon as possible after closing date of search. This is for a regular 100%, 12-month Academic Professional position in the University Library.

 

Duties and Responsibilities: The University of Illinois Urbana Champaign seeks an innovative and knowledgeable professional to serve in the position of E-Serials Bibliographic Control Specialist. This is an academic professional position for an entry level librarian with the requisite skills or course work or for a non-MLS professional with appropriate experience and skills. This position is largely responsible for developing and implementing library’s e-serials bibliographic control policy and practice. Under the direction of the Head of Content and Access Management, s(he) is to work to establish efficient work procedures and maintain high standards of both quality and production of bibliographic control for the Library's large collection of serials. The E-Serials Bibliographic Control Specialist will work in the Content Access Management unit within the Technical Services Division. The position will work in a team environment with those Division faculty and staff responsible for the cataloging and management of e-serials and maintenance of serials in all formats.

 

This position may participate in research activity regarding issues in bibliographic control in digital library environments and the impact of implementing emerging cataloging standards in user services and discovery services. 

 

As the information landscape is changing, this position may be asked to cover additional and evolving services or functions related to enhancing the discovery and delivery of library content.

 

Qualifications: Required: ALA accredited master’s degree in library or information science; Demonstrated supervisory experience; Serials cataloging experience in an academic or research library setting or cataloging experience with electronic resources; Familiarity with cataloging rules, standards, and tools such as MARC, RDA, AACR2, LCSH, and CONSER standards; Solid computer skills including spreadsheet and database applications; Effective organizational, interpersonal, and communication skills; Ability to work independently as well as cooperatively and flexibly with a wide variety of staff in a rapidly changing environment.  See https://jobs.illinois.edu for Preferred.

 

To Apply:  To ensure full consideration, please complete your candidate profile at https://jobs.illinois.edu and upload a letter of interest, resume, and contact information including email addresses for three professional references. Applications not submitted through this website will not be considered. For questions, please call: 217-333-8169.

 

Deadline:  In order to ensure full consideration we urge candidates to submit application materials on or before October 24, 2014

 

 

Illinois is an Affirmative Action /Equal Opportunity Employer and welcomes individuals with diverse backgrounds, experiences, and ideas who embrace and value diversity and inclusivity.

www.inclusiveillinois.illinois.edu



Myung-Ja "MJ" Han
Metadata Librarian
220 Main Library
University of Illinois at Urbana Champaign
1408 W. Gregory Dr. (MC-522)
Urbana, IL 61801
217-333-9515 (Main Library)
217-244-7809 (Grainger)
Jennifer Eustis | 2 Oct 16:35 2014
Picon

coordinates in MODS

Hello,

 

I’m working with a data set that includes bounding box information as well as orientation, scale and projection. As you know, MODS currently has the wrapper cartographics where you can record scale, project and coordinates. However, coordinates is just one field. The only attributes in 3.5 are the global ones or lang; xml:lang, script; transliteration. Is there any way, to enhance this MODS element coordinates? It would be great to distinguish center point from a bounding box. Also with a bounding box, it would be great to be able to separate and distinguish the 4 corners, S W N E. There is also no element for orientation. What do people think?

 

Best,

Jennifer

Meyer, Sebastian | 2 Oct 16:03 2014
Picon

Multiple identifiers for one person

Hi,

 

I am currently working on a MODS profile for our new Fedora Commons-based repository for open access publication services. All went well until I stumbled upon authors who had several associated IDs (ORCID, Scopus AuthorID, ResearcherID, GND, etc.). So obviously I cannot encode them like I would normally do, since this allows only for a single identifier:

 

//name[ <at> authorityURI="http://orcid.org"][ <at> valueURI="http://orcid.org/0000-0003-1419-2405"]/...

 

How would you handle this? Is there any valid way of associating more than one identifier with a single person? Repeating the //name block with different identifiers wouldn't solve the problem since that would be interpreted as having several distinct authors who just happen to have the same names (because their given identifiers differ).

 

The obvious solution would be to use //identifier as a repeatable child of //name. I am actually surprised that this isn't allowed, yet. May I suggest adding it in the next MODS schema release? Or is there a different approach I am missing?

 

Sincerely,

Sebastian

 

--

Sebastian Meyer

Head of Digital Library Dep.

 

Saxon State and University Library Dresden (SLUB)

IT Department

01054 Dresden, Germany

Tel.: +49 351 4677 206 | Fax: +49 351 4677 711

E-Mail:  sebastian.meyer-9q37W/UCdAvod10D2ZLB3g@public.gmane.org

 

http://www.slub-dresden.de

 

Scott Carlson | 15 Sep 20:51 2014

Job Announcement: Database & Metadata Management Coordinator - Houston, TX

-- Apologies for Cross-Posting --

Rice University is seeking a creative, dynamic, service-oriented Database &
Metadata Management Coordinator. The successful candidate will provide
leadership in performing and managing bibliographic data quality control,
database maintenance and problem resolution. The position reports to the
Head of Cataloging and Metadata Services in Technical Services.

Responsibilities:  Coordinates authority control of both MARC and non-MARC
metadata to ensure that they meet local and national standards. Develops new
and effective approaches to quality control, consulting with various
stakeholders as appropriate. Serves as a liaison to authority and database
enrichment vendors and manages the loading and quality control for
vendor-supplied data. Collaborates with other staff to provide leadership in
transitioning the department to a post-MARC communication format as we
continue to contribute metadata to the local institutional repository and
proactively explore linked data, the semantic Web and BIBFRAME. Assists in
and/or manages special projects undertaken by the Department as assigned by
the Department Head. Participates in departmental and library-wide
committees and work groups established to further various aspects of the
Fondren Library mission. May lead project teams. Assists in other cataloging
activities as needed.

Required Qualifications:
-ALA-accredited Master's degree in Library Science
-two years of successful related experience in quality & authority control
of MARC and non-MARC metadata
-some successful project management experience, preferably in an academic
library.
-Excellent oral and written communication skills.
-Project management skills.
-Proven ability to solve problems.
-Leadership and training skills and an ability to reach consensus with
diverse constituencies.
-Ability to recommend solutions in areas not under direct supervision.
-Flexibility in performing different tasks as library needs change.
-Commitment to enhancing services through teamwork.
-Ability to prioritize work to ensure that departmental and library goals
are realized.
-Demonstrated commitment to staff development and continuing education.
-Ability to work without close supervision.
-Thorough knowledge of MARC and non-MARC metadata standards and practices
(e.g. Dublin Core, EAD, MODS, METS, etc.).
-Knowledge of emerging trends and practices with linked data, semantic web
applications, BIBFRAME, and authority/identifier initiatives (e.g. VIAF,
ORCID, ISNI). 
-Experience with vendor authority control processes, preferably Marcive
authorities processing.
-Experience with loading large vendor record sets.
-Knowledge of database maintenance practices, including experience using
global changes to clean up data.
-Experience creating and manipulating data sets; experience with metadata
crosswalks.
-Knowledge of the new cataloging standard, Resource Description and Access
(RDA).
-Knowledge of OCLC.
-Knowledge of integrated library systems, preferably Sirsi. 
-High level of proficiency using MarcEdit.
-Knowledge of institutional repositories platforms, preferably DSpace.

Preferred qualifications:  Experience with XML, XSLT, and/or other tools or
macros for large-scale editing/transforming of metadata; experience with
developing macros and/or scripts to enhance productivity

Salary & benefits:  $52,000 minimum, with hiring salary commensurate with
experience and qualifications; no state or local income tax; 21 benefit
days; 8 study days; a range of retirement options including TIAA/CREF;
health and life insurance; and tuition waiver.

Environment: Rice University provides a stimulating work environment, with
opportunities to participate in the delivery of innovative library services
supported by leading edge technologies. Fondren Library
(http://www.rice.edu/fondren) is a research library with more than 2.8
million volumes and more than 141,000 subscriptions, including titles
available through aggregators. The Library has a state-of-the-art off-site
shelving facility. An active program of digital resource delivery and
development is grounded in successful collaboration among library and
University staff from Digital Scholarship Services, other library
departments and University information technology staff.

Houston is a vibrant, multicultural city, with world-class visual and
performing arts ranging from the traditional to the avant-garde. The fourth
largest city in the country, Houston enjoys a moderate cost of living and
easy proximity to the Gulf Coast. For more information, see:
http://www.explore.rice.edu/explore/General_Information.asp.

Applications received by October 10, 2014 will receive first consideration.
Please apply with cover letter, resume, and the names, titles, addresses,
telephone numbers, and e-mail addresses of three references at:
https://jobs.rice.edu/applicants/Central?quickFind=54454. Inquiries: Melinda
Reagor Flannery at (713) 348-3773 or reagor@... Rice
University is an
Equal Opportunity Employer – Females/Minorities/Veterans/Disabled/Sexual
Orientation/Gender Identity.

--

-- 
Scott Carlson
Metadata Coordinator
Rice University, Fondren Library
scarlson@...

Meehleib, Tracy | 11 Aug 21:49 2014
Picon

MARCXML to MODS 3.5 -- XSLT 1.0 (Revision 1.101) Announcement

MARCXML to MODS 3.5 -- XSLT 1.0 (Revision 1.101) Announcement

The Library of Congress' MARCXML to MODS 3.5 (XSLT 1.0 Revision 1.101) is now available via the Library of Congress' MODS Web site and at <http://www.loc.gov/standards/mods/v3/MARC21slim2MODS3-5.xsl >--it incorporates edits made in response to comments received since the release of Revision 1.96.

The MODS 3.5 XSLT is based on the MARC to MODS 3.5 mapping made available by the Library of Congress and last updated in May of 2014 <http://www.loc.gov/standards/mods/mods-mapping.html>.

Please note that content standards and practices using MARC vary among institutions, and sometimes within an institution over time or between types of collections or materials. No one stylesheet can deal appropriately with all variations in the use of MARC. The mapping decisions underlying the changes we have made, as well as the decisions underlying the LC stylesheet should be tested on sample records to determine whether the results are as desired or whether the institution needs to modify the stylesheet for a particular collection of records.

General questions about the mapping may be directed to the MODS Editorial Committee members via ndmso-+hwoy1Po9Oc@public.gmane.org. Specific questions about the stylesheet may be addressed to Tracy Meehleib at tmee-+hwoy1Po9Oc@public.gmane.org .

Thank you,

Tracy

Tracy Meehleib

Network Development and MARC Standards Office
Library of Congress
101 Independence Ave SE

Washington, DC 20540-4402
+1 202 707 0121 (voice)
+1 202 707 0115 (fax)

tmee-+hwoy1Po9Oc@public.gmane.org

 

Rebecca Guenther | 11 Aug 21:11 2014
Picon

AMIA cataloging and metadata workshop

This workshop might be of interest to those of you managing moving image (analog and digital) materials. It’s being held as a pre-conference workshop at the Association of Moving Image Archivists (AMIA) conference, but attendees can register separately. This year the conference has a special stream on “digital” aspects of preserving and providing access to digital AV content. More info on the conference in general: www.amiaconference.net

 

AMIA Cataloging & Metadata Workshop | October 7-8, 2014 | Savannah, Georgia

The 2014 edition of this bi-annual workshop includes new content and offers attendees—past and future alike—a workshop that emphasizes practical implementation through the use of hands-on exercises and addresses how the attendee can concretely integrate new models for description into their current workflows and environments.    The two-day program moves the attendee from concept to implementation starting with cataloging principles and metadata concepts that form the basis for describing and providing access to moving images in an evolving media and media technology environment. The workshop includes information about the role of cataloging for analog and digital asset management; the value, purpose and application of metadata and cataloging standards; management of resources through their life cycles; descriptive, structural, and administrative metadata (including rights and preservation metadata); and, data models and data mapping. Dynamic presentations encompass film, video, digital, and broadcast materials and include interactive exercises to put cataloging and metadata concepts directly into practice. 

 


Please excuse duplication of this message.

Rebecca







Melanie Wacker | 8 Aug 22:27 2014

hierarchicalGeographic

Hello,
the MODS Editorial Committee would like to follow up on a proposal to introduce some changes to the MODS <hierarchicalGeographic> element.  While there are no specific plans for a MODS version 4 at this point, it would be a major overhaul of MODS. However, several useful changes to the <hierarchicalGeographic> element could be introduced in MODS 3.6.

A previous proposal was sent out for discussion on Dec. 27, 2013.
This proposal can be found here:
 http://listserv.loc.gov/cgi-bin/wa?A2=ind1312&L=mods&T=0&P=2177

Responses:

http://listserv.loc.gov/cgi-bin/wa?A1=ind1401&L=mods&D=0&H=0&O=T&T=0
http://listserv.loc.gov/cgi-bin/wa?A1=ind1402&L=mods&D=0&H=0&O=T&T=0

The MODS EC revised the proposal based on the feedback received and is now soliciting comments on the new proposal, see below.
We would like to hear from you by Sept. 5, 2014

Regards,
Melanie Wacker

on behalf of the MODS EC

 

MODS HierarchicalGeographic Proposal


1      Specific Proposal 

1.1    State and Province
<province> will be deprecated;  <state> will be re-defined:
<state>-- Includes first order political jurisdictions under countries, such as states, provinces, cantons, Länder, etc. regardless of what they are called in the particular country.

See Commentary and Examples:  1.

1.2    New Attributes to Indicate Place Types


Attributes <at> areaType, <at> regionType, and <at> sectionType will be defined for elements <area>, <region>, and <citySection>  respectively.  These would of course be optional.

See Commentary and Examples:  2.

 

1.3    Indication of hierarchical level

 

Attribute <at> level will be defined for all place type elements to indicate hierarchical level. It would of course be optional.

See Commentary and Examples:  3.

1.4      Authority


The authority attributeGroup (authority, authorityURI, and valueURI)  will be added to all place type elements.
 

1.5    Places that no longer exits

Attribute <at> period will be defined. Its presence will indicate that the described entity once existed but no longer exists.  Its value would be a hint of when it existed (it could simply be a date).

            See Commentary and Examples:  4.

 

2      Commentary and Examples

 

  1. The way MODS currently handles first level political jurisdictions -- i.e. first level below the country -- is not consistent. It was brought out that in the MARC 662 there is a subfield called "first order political jurisdiction". In MODS, both <state> and <province> are used for first order political jurisdictions depending upon what they're called in the particular country-- but the guidelines say the following:

<state> – Includes first order political divisions called states within a country, e.g. in U.S., Argentina, Italy. Use also for France département.

<province> – Includes first order political divisions called provinces within a country, e.g. in Canada.

So first order political divisions mostly go under <state> unless they're called <province>. And we're silent on what they call them in other countries.

The committee thinks it desirable to put all first order political divisions under one element. The term "first order political division" or "first order political jurisdiction" is rather unwieldy. So the proposal is to deprecate province and define <state> as all first order political jurisdictions.

  1. This replaces the earlier proposal to define new element <placeOther> and attribute <at> otherType, to accommodate other types of places that don't have their own element.  Instead,  group them together under <area>, <region> or  <citySection> as appropriate (area is used for non-jurisdictional places, region for jurisdictional,  and <citySection> may be used for either ) and indicate the place type with the corresponding attribute, <at> areaType,   <at> regionType, or <at> sectionType.

<citySection> for example is currently defined as:

<citySection>-- Name of a smaller unit within a populated place, e.g., neighborhoods, parks, or streets

Thus, citySection is a broad term that can be used without the <at> sectionType attribute, but if you want to designate a specific type of city section you  could say

<citySection sectionType="neighborhood" >

for formally established neighborhoods, or

            <citySection sectionType="street>".

Note that the use of "city" here doesn't preclude  towns.

<area> could take an <at> areaType attribute to accommodate some of those areas that have been suggested-- national parks, rivers, Indian reservation, etc.

Example:

    <hierarchicalGeographic>

            <country>United States</country>

            <state>Rhode Island</state>

            <city>Providence</city>

            <citySection citySectiontype="neighborhood">Blackstone</citySection>

   </hierarchicalGeographic>

  1. When the level of elementA is less than the level of element, then elementA is higher in the hierarchy than element. It is recommended that levels begin with 1 and are consecutive, however this is not mandated. Levels could, for example, be 3 , 5, and 9.

There is no need for <at> level  for simple cases like the following where the hierarchy is easily inferred:

            <country>United States</country>

            <state>Rhode Island</state>

            <city>Providence</city>

 But there are a few cases where <at> level would be useful:

  • The actual hierarchy of the existing place types for hierarchicalGeographic isn't always clear, and in some cases depends on the context.

  • It will be useful to be able to indicate that two places have the same level.

  • In cases where the same place type is supplied more than once, their levels relative to one-another are not always clear.

 

 

 To elaborate of the latter two points:

 Consider the following example, where Blackstone is a sub-neighborhood of East Side, in Providence.

            <country>United States</country>

            <state>Rhode Island</state>

            <city>providence</city>

         <citySection citySectiontype="neighborhood" level="1">East Side</ citySection >

      < citySection citySectiontype="neighborhood" level="2">Blackstone</ citySection >

 Another example, consider Massachusetts Avenue which runs through Lincoln Park within Capitol Hill in Washington DC. Say you want to identify that section of Mass Ave  within the park: 

           <state>District of Columbia</state>

            <city>Washington</city>

            <citySection citySectionType ="neighborhood" level="1">Capitol Hill</ citySection>

            < citySection citySectionType =”park”  level="2">Lincoln Park</ citySection>    

          <citySection citySectionType =”street” level="2">Massachusetts Avenue</citySection>

Whenever the level is the same for two places the intersection is indicated. This example indicates the intersection of the two level 5 entities.  

 

  1. The following example indicates the portion of the Oregon Trail within Idaho that existed during the gold rush: 

           <state level="2">Idaho</state>

            <area  level="3"type="trail" period="gold rush">Oregon Trail</area>

Another Example:

            <continent>Europe</continent>

            <country period=”1945-1990”>East Germany</country>
Elizabeth Post | 4 Aug 15:36 2014
Picon

METS Workshop Invitation

All are invited to participate and provide feedback to the METS Editorial Board on a new draft version of the METS schema, METS 2.0, at a workshop being held in London as part of Digital Libraries 2014, an event organized by the ACM/IEEE Joint Conference on Digital Libraries (JCDL 2014) and the International Conference on Theory and Practice of Digital Libraries (TPDL 2014). 


The Metadata Encoding and Transmission Standard (METS) 1.x schema has an established community of users many of whom are moving toward the use of newer technologies such as those of the Semantic Web and linked data for their digital content and metadata. In this workshop, entitled METS Now, and Then… Discussions of Current and Future Data Models, participants will develop an understanding of the data models underlying some canonical uses of the existing METS schema as illustrated by a panel of experienced METS implementers.  The explication of data models will provide a contextual basis for the description of a next generation METS (2.0) data model.  Participants will be invited to participate in the refinement of the METS 2.0 data model being developed by the METS Editorial Board, and discuss options for serialization of the data model.


The workshop will take place over two half days:  Thursday, September 11 (afternoon) andFriday, September 12.  For more information and registration, please visit the Digital Libraries 2014 site or contact Betsy Post (betsy.post-Qs1XVtlgrJU@public.gmane.org).


Please note that the last day for discounted early registration is Monday, August 11.

Meehleib, Tracy | 30 Jul 21:10 2014
Picon

LC NDMSO survey monkey XSLT 1.0 vs 2.0

Dear MODS Users,

 

The Library of Congress would like to better understand how its MODS stylesheets are being used. If you use any of LC’s MODS-related  XSLTs to convert records, and haven’t already responded to this survey, please take a moment to fill it out:  

< https://www.surveymonkey.com/s/DVQ3J9T >.  

 

Thank you!

 

Tracy

 

Tracy Meehleib

Network Development and MARC Standards Office
Library of Congress
101 Independence Ave SE
Washington, DC 20540-4402
+1 202 707 0121 (voice)
+1 202 707 0115 (fax)

tmee-+hwoy1Po9Oc@public.gmane.org

 

 

McCallum, Sally | 29 Jul 23:10 2014
Picon

AV study posted

Just posted on the BIBFRAME (BF) web site is a study carried out by Audiovisual Preservation Solutions for the Library of Congress concerning an appropriate model for AV material and relating that to the BF model:  BIBFRAME AV Modeling Study: Defining a Flexible Model for Description of Audiovisual Resources.   It discusses the special characteristics of AV material that make it different from textual and other media and makes some general recommendations.  With the increasing impact of AV as information resources and the need to preserve material in those media, special attention to it is appropriate as we develop BIBFRAME.

 

This report was carried out in close consultation with the Library of Congress’s National Audiovisual Conservation Center (NAVCC) staff in Culpeper, Virginia, a vast archive that preserves and serves AV resources.  The report examines a number of proposed community models such as FRBR/RDA, FIAF, OLAC, indecs, Variations, PBCore, EBCore and others that inform the analysis.    The recommendations will become considerations for the BF model development as there are various ways the special attributes of these media could be accommodated.

 

The report is composed of a base document (the analysis, AV model, and recommendations) with appendices that give more detail about situations encountered with AV material.

 

As usual, comments, concerns, and discussion are encouraged via the BIBFRAME listserv (see the BIBFRAME home page/contacts) or direct to bfcomment-+hwoy1Po9Oc@public.gmane.org .

 

Sally

 

***********************************

Sally H. McCallum

Chief, Network Development and MARC Standards Office

Library of Congress, 101 Independence Ave., SE

Washington, DC 20540  USA

smcc-+hwoy1Po9Oc@public.gmane.org

Tel: 1-202-707-5119 – Fax 1-202-707-0115

***********************************

 

 


Gmane