Treat OCLC Work identifiers as bf:Work bf:Identifiers #101
Conversation
|
This is an interesting request, but I'd like to see some MARC examples which illustrate this configuration. Do any exist? |
|
Yes, Laurentian University enriched the records in their catalogue by using OCLC's xID service (RIP) to add 024 entries for Work entity URIs. The original purpose was to express the relationship in the corresponding HTML via RDFa with schema:exampleOfWork (per the Evergreen library system's defaults). But, when constrained by matching "worldcat.org/entity/work/", it offers a clear path forward for one subset of possible Work identifiers in the BIBFRAME conversion process. So, a couple of examples in the wild:
|
|
Re: the Evergreen default for 024 and OCLC Work entities, that was added in March 2015 as part of release 2.8.0 (about halfway through the OPAC enhancements section): http://docs.evergreen-ils.org/2.8/_evergreen_2_8_0_release_notes.html |
The OCLC Work identifier URIs are intended to group like works together, thus if found they should be turned into an Identifier at the level of a bf:Work instead of at the bf:Instance level. Signed-off-by: Dan Scott <[email protected]>
dbs
force-pushed
the
oclc_work_entities_as_work_identifiers
branch
from
f204eec to
8db4be7
Compare
3 participants
The OCLC Work identifier URIs are intended to group like works together, thus
if found they should be turned into an Identifier at the level of a bf:Work
instead of at the bf:Instance level.
Signed-off-by: Dan Scott [email protected]