Linked data: link out to major entities such as LoC and OCLC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
* Evergreen master
RIght now we're publishing lots of structured data--that is, schema.org classes with properties--but almost all of their values are strings. That's been a good start, but we need to connect up to the rest of the linked data cloud, and we have some very easy places to start:
1) If we have a LCCN, we can link to the corresponding Library of Congress record
2) If we have an OCLC number, we can link to the corresponding WorldCat record
3) If we have a 024 with a subfield 2 value of "uri", we can link to that universal resource identifier
These simple steps will give search engines and other aggregators crawling our data much more to work with, because they can recognize that we're describing a resource that is the same as something else that has much more linked data.
Changed in evergreen: | |
milestone: | none → 2.next |
tags: | added: linkeddata |
Changed in evergreen: | |
milestone: | 2.next → 2.8-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Added http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbs/lp1402921_ linkout_ schema_ sameas - the first commit comes from bug 1402905, which should be resolved first, but the most recent commit contains the core of this actual feature.