Difference between revisions of "Step 2.11"

From AC Wiki
Jump to: navigation, search
(Add URIs to Authority Records)
(Step 2.11: Identities Management)
Line 1: Line 1:
 
==Step 2.11: Identities Management==
 
==Step 2.11: Identities Management==
 
[[Image:a2-11.png]]<br><br>
 
[[Image:a2-11.png]]<br><br>
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.
+
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn link]) within your records. Please check with your project manager for any fees that may be associated with these options.
  
 
===Add $0 to Access Points===
 
===Add $0 to Access Points===
Line 43: Line 43:
  
 
===Add URIs to Authority Records===
 
===Add URIs to Authority Records===
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.
+
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html link]) and ISNI ([http://www.isni.org/ link]) URIs to insert into matching authorities.
  
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).
+
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html link]).
  
 
Here is an example of an authority record delivered with both 024 and 92X fields populated:
 
Here is an example of an authority record delivered with both 024 and 92X fields populated:

Revision as of 09:07, 20 October 2016

Step 2.11: Identities Management

A2-11.png

MARS 2.0 offers two types of identities management options for identifiers or URIs (link) within your records. Please check with your project manager for any fees that may be associated with these options.

Add $0 to Access Points

Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.

This particular option allows us to add the $0 at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.

Here is an example of a before/after record adding a matching authority identifier:

 
 original record:
 100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.
 245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
 650 #0 $a Anatomy, Artistic.
 650 #2 $a Anatomy, Artistic.
 
 updated record:
 100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator $0 nr 99034050 
 245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
 650 #0 $a Anatomy, Artistic. $0 sh 85004836 
 650 #2 $a Anatomy, Artistic. $0 D000716 
 

Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.

Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding $0:

 
 original record:
 100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.
 245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
 650 #0 $a Anatomy, Artistic.
 650 #2 $a Anatomy, Artistic.
 
 updated record:
 100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator $0 http://id.loc.gov/authorities/names/nr99034050
 245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
 650 #0 $a Anatomy, Artistic. $0 http://id.loc.gov/authorities/subjects/sh85004836
 650 #2 $a Anatomy, Artistic. $0 http://id.nlm.nih.gov/mesh/D000716
 

Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our default is to add the identifier only in the $0. One thing to note is that, while we also default to adding the $0 at the end of the access point, we can also add it after the last matching portion of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.

Add URIs to Authority Records

With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF (link) and ISNI (link) URIs to insert into matching authorities.

One of our clients decided to use 92X fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated identifiers added to 024 fields (link).

Here is an example of an authority record delivered with both 024 and 92X fields populated:

 
 001 ## no2001000753
 024 7# $a no2001000753 $2 lccn
 024 7# $a 23238834 $2 viaf
 024 7# $a 0000000116075005 $2 isni
 100 1# $a Volkmann, Hans
 920 ## $a http://id.loc.gov/authorities/names/no2001000753
 921 ## $a http://viaf.org/viaf/23238834
 922 ## $a http://isni.org/isni/0000000116075005
 

This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.

links

2.1 - 2.2 - 2.3 - 2.4 - 2.5 - 2.6 - 2.7 - 2.8 - 2.10 - 2.11
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0