https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25801
--- Comment #19 from Marcel de Rooy <[email protected]> --- (In reply to David Cook from comment #18) > RDF subjects was my first thought, although reading more about RPC and REST > APIs and thinking that having a canonical item URL (or PID) could be useful > for a REST API (better to return a URL rather than an itemnumber for > instance). > I was wondering if you had a particular use case that you plan to use this > for in the short term is all. Like is the HTML representation important in > your use case? Or is it just to uniquely identify the resource (say for a > RDF subject or REST API)? Yes, the landing page of the item persistent identifier (URL) is not that important, but I do want to be able to dereference it. Including an HTML representation when that would be the result of content negotiation. But surely the main thing is a unique resource identifier in the form of a URL. We will be using something like https://id.rijksmuseum.nl/3012345 Our institutional PID resolver knows (as a partial or meta resolver) how to pass library PIDs to the library PID resolver. Which would use opac-detail for HTML in case of a biblio or item. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
