For those of you who utilize URI Enrichment services, we now have another set of fields that will benefit: 34X.

The 34X URIs come from the RDA registry and will be maintained in various list sets within our processing. Since these are maintained by lists instead of authority records, there are separate rules that your Project Manager will need to turn on in order to incorporate this addition. Please let her know if you'd like to add the 34X URIs.

Because previous practice for 34X has been to include a generic $2 rda and has allowed for multiple subfields to be in a single 34x field, our URI processing will split pre-existing 34X into a single term/subfield per field based on specific term lists, add the URI, and will then change $2 rda to the appropriate code.

Example:

Before:

344 __ ▼adigital▼boptical▼gsurround▼hDolby Digital 5.1▼2rda

344 __ ▼adigital▼boptical▼gsurround▼hDolby Digital 2.0▼2rda

345 __ ▼awidescreen (2.40:1)▼b24 fps▼2rda

346 __ ▼bNTSC▼2rda

347 __ ▼avideo file▼bDVD video▼eRegion 1▼2rda

After:

340 __ ▼b4 3/4 in.▼2rda

344 __ ▼hDolby Digital 5.1▼2rda

344 __ ▼hDolby Digital 2.0▼2rda

344 __ ▼adigital▼2rdatr▼0http://rdaregistry.info/termList/typeRec/1002

344 __ ▼boptical▼2rdarm▼0http://rdaregistry.info/termList/recMedium/1001

344 __ ▼gsurround▼2rdacpc▼0http://rdaregistry.info/termList/configPlayback/1004

345 __ ▼awidescreen (2.40:1)▼b24 fps▼2rda

346 __ ▼bNTSC▼2rdabs▼0http://rdaregistry.info/termList/broadcastStand/1002

347 __ ▼bDVD video▼2rda

347 __ ▼avideo file▼2rdaft▼0http://rdaregistry.info/termList/fileType/1006

347 __ ▼eRegion 1▼2rdare▼0http://rdaregistry.info/termList/RDARegionalEncoding/1002

NOTE: Any term that does not currently fit an RDA Registry vocabulary will not receive a $0 nor will the $2 be corrected. As terms & URIs are added, we’ll update our lists accordingly

Just as a reminder, the following fields are currently available for URI enrichment:

043
050
33X
34X
Access points

Do let us know if you have any questions!