Difference between revisions of "Step 2.12"
(→Add $0 to Access Points) |
(→Add $1 URIs to Access Points) |
||
| (14 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ==Step 2. | + | ==Step 2.12: Identities Management== |
| − | [[Image: | + | [[Image:A2-12new.jpg]]<br><br> |
| − | MARS 2.0 offers | + | MARS 2.0 offers multiple 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. |
===Add $0 to Access Points=== | ===Add $0 to Access Points=== | ||
| Line 40: | Line 40: | ||
</font> | </font> | ||
| − | 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 | + | 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 full URI 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. |
| + | |||
| + | At the end of 2019 we updated the URI processing to better reflect the "best practices" for Name/Title matches when that Name/Title appear in a 1XX & 240 field. New best practices are to include a URI for just the name in the 1XX field and a URI for the Name/Title in the 240 field. | ||
| + | <font size="3"> | ||
| + | '''original record''': | ||
| + | 100 1# $a Alderman, Naomi, $e author. | ||
| + | 240 10 $a Power. $l Spanish | ||
| + | |||
| + | '''updated record''': | ||
| + | 100 1# $a Alderman, Naomi, $e author. $0 http://id.loc.gov/authorities/names/n2006034931 | ||
| + | 240 10 $a Power. $l Spanish $0 http://id.loc.gov/authorities/names/no2018156991 | ||
| + | </font> | ||
| + | |||
| + | We have two alternative options to this new standard for the 1XX/240. Please notify us if you would prefer either of these alternates. | ||
| + | 1. Add name-only URI in the 1XX field; no URI to the 240 | ||
| + | 2. Add name/title URI to the 240 only; no URI to the 1XX | ||
| + | |||
| + | '''ILS Note:''' The TIND ILS requires a slightly different approach to placement of the $0 with the identifier. Instead of appearing at the end of the string, the $0 for TIND users will appear after the largest matching string. This means that you may have a $0 after a $a$x combination and a different $0 after a $z. This placement of the $0 ensures that global updates occur on the correct chuck of your Access Point when updated authority records are loaded into the system. | ||
| + | <font size="3"> | ||
| + | '''original record''': | ||
| + | 100 1# $a Freccia Marino, $d 1503-1566. | ||
| + | 240 10 $a De subfeudis baronum & investituris feudorum | ||
| + | 245 10 $a Marini Frecciae, patricij Neapolitani militisque clariss. ciuitatis literae ... Commentarij feudales : $b in tres libros partiti. | ||
| + | 650 #0 $a Feudal law $z Italy $z Naples (Kingdom). | ||
| + | 650 #0 $a Feudal law $z Italy $z Sicily. | ||
| + | |||
| + | '''updated record''': | ||
| + | 100 1# $a Freccia Marino, $d 1503-1566. <font color='blue'>$0 n 87890918 </font> | ||
| + | 240 10 $a De subfeudis baronum & investituris feudorum <font color='blue'>$0 n 87890919 </font> | ||
| + | 245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon. | ||
| + | 650 #0 $a Feudal law <font color='blue'>$0 sh 85047982 </font> $z Italy <font color='blue'>$0 n 79021783 </font>$z Naples (Kingdom). | ||
| + | 650 #0 $a Feudal law <font color='blue'>$0 sh 85047982 </font> $z Italy <font color='blue'>$0 n 79021783 </font>$z Sicily. | ||
| + | </font> | ||
| + | |||
| + | ===Add $4 to Access Points=== | ||
| + | In days past, the $4 in access points was defined for use for the relator "code" and was often used in place of the $e relator term. The $4 has now been redefined to ALSO include the URI for the relator. Our process will check the $e relator term and/or the $4 relator code against id.loc.gov/vocabulary/relators to identify the appropriate URI for the relator. | ||
| + | |||
| + | Examples: | ||
| + | 100 1_ $a Delaplanche, Chantal, $e author. $4 http://id.loc.gov/vocabulary/relators/aut | ||
| + | 700 1_ $a Kirby, Luke. $4 act $4 http://id.loc.gov/vocabulary/relators/act | ||
| + | |||
| + | |||
| + | ===Add $0 to non-Access Points=== | ||
| + | With the continued conversations of moving beyond MARC to a linked data environment, the greater library community is continuing to explore other | ||
| + | MARC fields that could potentially have URIs added. The MARS 2.0 service can currently add URIs to the following MARC fields: 043, 050, 33X, 34X. | ||
| + | Examples: | ||
| + | 043 ## $a n-us--- $0 http://id.loc.gov/vocabulary/geographicAreas/n-us | ||
| + | 050 14 $a KF27 $b .E5525 2010b $0 http://id.loc.gov/authorities/classification/K | ||
| + | 336 ## $a text $2 rdacontent $0 http://rdaregistry.info/termList/RDAContentType/1020 | ||
| + | 337 ## $a unmediated $2 rdamedia $0 http://rdaregistry.info/termList/RDAMediaType/1007 | ||
| + | 338 ## $a volume $2 rdacarrier $0 http://rdaregistry.info/termList/RDACarrierType/1049 | ||
| + | |||
| + | 340 ## $a plastic $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1029 | ||
| + | 340 ## $g polychrome $2 rdacc $0 http://rdaregistry.info/termList/RDAColourContent/1003 | ||
| + | 340 ## $a metal $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1022 | ||
| + | 344 ## $a digital $2 rdatr $0 http://rdaregistry.info/termList/typeRec/1002 | ||
| + | 344 ## $b optical $2 rdarm $0 http://rdaregistry.info/termList/recMedium/1001 | ||
| + | 344 ## $c 1.4 m/s | ||
| + | 347 ## $b Blu-ray $d 1920 x 1080p $2 rda | ||
| + | 347 ## $a video file $2 rdaft $0 http://rdaregistry.info/termList/fileType/1006 | ||
| + | |||
| + | NOTE: Any incoming 34X will attempt to be split based on the RDA Registry vocabularies. If terms do not match a vocabulary, they will remain as they were in the incoming field. | ||
| + | |||
| + | ===Add $1 URIs to Access Points=== | ||
| + | In addition to having a $0 with the URI for the authority added, you may also opt to have a $1 for a Real World Object (RWO) added. Current sources available are WikiData, LC Agents, the Virtual International Authority File (VIAF), and the International Standard Name Identifier (ISNI). | ||
| + | Example: | ||
| + | 100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator. $1 http://id.loc.gov/rwo/agents/nr99034050 | ||
| + | $1 https://www.wikidata.org/entity/Q987687 $1 http://viaf.org/viaf/64206515 $1 http://isni.org/isni/0000000122809802 | ||
===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 | + | 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 | + | 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: | ||
| Line 54: | Line 121: | ||
024 7# $a <font color='blue'>0000000116075005</font> $2 isni | 024 7# $a <font color='blue'>0000000116075005</font> $2 isni | ||
100 1# $a Volkmann, Hans | 100 1# $a Volkmann, Hans | ||
| − | 920 ## $a | + | 920 ## $a http://id.loc.gov/authorities/names/no2001000753 |
| − | 921 ## $a | + | 921 ## $a http://viaf.org/viaf/23238834 |
| − | 922 ## $a | + | 922 ## $a http://isni.org/isni/0000000116075005 |
</font> | </font> | ||
| Line 62: | Line 129: | ||
==links== | ==links== | ||
| − | <center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2. | + | <center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] |
<hr> | <hr> | ||
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center> | [[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center> | ||
[[category:Profile Guide]] | [[category:Profile Guide]] | ||
Latest revision as of 10:24, 18 June 2024
Contents
Step 2.12: Identities Management
MARS 2.0 offers multiple types of identities management options for identifiers or URIs (link) within your records.
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 full URI 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.
At the end of 2019 we updated the URI processing to better reflect the "best practices" for Name/Title matches when that Name/Title appear in a 1XX & 240 field. New best practices are to include a URI for just the name in the 1XX field and a URI for the Name/Title in the 240 field.
original record: 100 1# $a Alderman, Naomi, $e author. 240 10 $a Power. $l Spanish updated record: 100 1# $a Alderman, Naomi, $e author. $0 http://id.loc.gov/authorities/names/n2006034931 240 10 $a Power. $l Spanish $0 http://id.loc.gov/authorities/names/no2018156991
We have two alternative options to this new standard for the 1XX/240. Please notify us if you would prefer either of these alternates.
1. Add name-only URI in the 1XX field; no URI to the 240 2. Add name/title URI to the 240 only; no URI to the 1XX
ILS Note: The TIND ILS requires a slightly different approach to placement of the $0 with the identifier. Instead of appearing at the end of the string, the $0 for TIND users will appear after the largest matching string. This means that you may have a $0 after a $a$x combination and a different $0 after a $z. This placement of the $0 ensures that global updates occur on the correct chuck of your Access Point when updated authority records are loaded into the system.
original record: 100 1# $a Freccia Marino, $d 1503-1566. 240 10 $a De subfeudis baronum & investituris feudorum 245 10 $a Marini Frecciae, patricij Neapolitani militisque clariss. ciuitatis literae ... Commentarij feudales : $b in tres libros partiti. 650 #0 $a Feudal law $z Italy $z Naples (Kingdom). 650 #0 $a Feudal law $z Italy $z Sicily. updated record: 100 1# $a Freccia Marino, $d 1503-1566. $0 n 87890918 240 10 $a De subfeudis baronum & investituris feudorum $0 n 87890919 245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon. 650 #0 $a Feudal law $0 sh 85047982 $z Italy $0 n 79021783 $z Naples (Kingdom). 650 #0 $a Feudal law $0 sh 85047982 $z Italy $0 n 79021783 $z Sicily.
Add $4 to Access Points
In days past, the $4 in access points was defined for use for the relator "code" and was often used in place of the $e relator term. The $4 has now been redefined to ALSO include the URI for the relator. Our process will check the $e relator term and/or the $4 relator code against id.loc.gov/vocabulary/relators to identify the appropriate URI for the relator.
Examples: 100 1_ $a Delaplanche, Chantal, $e author. $4 http://id.loc.gov/vocabulary/relators/aut 700 1_ $a Kirby, Luke. $4 act $4 http://id.loc.gov/vocabulary/relators/act
Add $0 to non-Access Points
With the continued conversations of moving beyond MARC to a linked data environment, the greater library community is continuing to explore other MARC fields that could potentially have URIs added. The MARS 2.0 service can currently add URIs to the following MARC fields: 043, 050, 33X, 34X.
Examples: 043 ## $a n-us--- $0 http://id.loc.gov/vocabulary/geographicAreas/n-us 050 14 $a KF27 $b .E5525 2010b $0 http://id.loc.gov/authorities/classification/K 336 ## $a text $2 rdacontent $0 http://rdaregistry.info/termList/RDAContentType/1020 337 ## $a unmediated $2 rdamedia $0 http://rdaregistry.info/termList/RDAMediaType/1007 338 ## $a volume $2 rdacarrier $0 http://rdaregistry.info/termList/RDACarrierType/1049
340 ## $a plastic $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1029 340 ## $g polychrome $2 rdacc $0 http://rdaregistry.info/termList/RDAColourContent/1003 340 ## $a metal $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1022 344 ## $a digital $2 rdatr $0 http://rdaregistry.info/termList/typeRec/1002 344 ## $b optical $2 rdarm $0 http://rdaregistry.info/termList/recMedium/1001 344 ## $c 1.4 m/s 347 ## $b Blu-ray $d 1920 x 1080p $2 rda 347 ## $a video file $2 rdaft $0 http://rdaregistry.info/termList/fileType/1006
NOTE: Any incoming 34X will attempt to be split based on the RDA Registry vocabularies. If terms do not match a vocabulary, they will remain as they were in the incoming field.
Add $1 URIs to Access Points
In addition to having a $0 with the URI for the authority added, you may also opt to have a $1 for a Real World Object (RWO) added. Current sources available are WikiData, LC Agents, the Virtual International Authority File (VIAF), and the International Standard Name Identifier (ISNI). Example:
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator. $1 http://id.loc.gov/rwo/agents/nr99034050 $1 https://www.wikidata.org/entity/Q987687 $1 http://viaf.org/viaf/64206515 $1 http://isni.org/isni/0000000122809802
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
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
