Designing our IRIs
#472
Replies: 1 comment
-
|
I’m just not sure about this at all. I’ve asked our head of ITS-DS to make sure we don’t have any policies or guidelines here at UW that would require us to shape IRIs in a certain way. If we don’t, we’re just going to have to come up with the best solution we can. Soon. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Minting IRIs Discussion
I have just pushed an update to the code that helps to ensure our minted IRIs remain unique by basing them off of the control number in 001.
I have also restructured the IRIs slightly, based heavily off of how marc2bibframe designed theirs.
IRIs are structured as follows:
For the main WEM stack:
[BASE]/[control number]wor,[BASE]/[control number]exp, and[BASE]/[control number]mane.g.
http://marc2rda.edu/fake/99162596149401452worFor opaque IRIs, they are structured similarly, but with an additional identifier created by the transform added as a hash URI.
[BASE]/[control number][type]#[generated id]. The type may berelWor,origMan,ite,nom,age,pla,tim, orconbased on what entity the IRI is minted for.e.g.
http://marc2rda.edu/fake/99115297060001452ite#d22e8053For IRIs where sources are provided and we want to allow for some automatic de-duplication, the structure is
[BASE]/[source]/[type]#[access point]. The control number is not used so that de-duplication can occur across records.e.g.
http://marc2rda.edu/fake/star/con#restrictionsunspecifiedandhttp://marc2rda.edu/fake/lcsh/age#unitedstatesdepartmentofagricultureofficeofthesecretaryAny input or thoughts on how we structure and mint IRIs is welcome and can go in this discussion.
Beta Was this translation helpful? Give feedback.
All reactions