Talk:Msc/E/id
From Steeple
Page imported from here.
[edit] 1 Do we need multiple identifiers?
One of the problems is that the identifiers may be local, in that sense we have a problem using an rss:guid ar an atom:id in this place. So we may need an <o:id domain="..."></o:id> type element. I.e. if a feed from ETH gets aggregated, the aggregator might have "ETH-123456" as id for the element, but ETH may have 123456
<rss:guid>ETH-123456</rss:guid> <o:id domain="ETH">123456</o:id>
(of course the two ids may be completely unrelated).
OAS: This neatly leads to the question whether persistent identifiers could be (one of) the identifiers: At least in the DOI world, a local prefix is part of the string. On the issue of having two (or more) ID, it certainly plays a role whether you work with a local handle and/or a registered one like DOI.
Bjoern 11:13, 16 September 2009 (UTC): Just to add some more thoughts: The <o:id> would be something that is passed 'up' to the syndication engine. It's really for situations where a local guid is not suitable for the aggregator, and so allows the institution to pass a different id to the syndication engine (the format of which is specified by the syndication engine). It might be <o:id>ox.ac.uk/something</o:id>.
Bjoern 15:41, 28 October 2009 (UTC): Update. Steeple now includes <s:id domain="...">id</s:id>, see http://purl.org/steeple/s:id
[edit] 2 Os Solution
We use an lecture recordings system identifier, it's: <administration server url>/lecutre/id to get not in trouble with identifier from different systems Nbirnbaum 14:48, 16 September 2009 (UTC)
[edit] 3 series id vs. item id
c.f. "latest episodes" feed witll nned series id at item level. Bjoern 14:54, 16 September 2009 (UTC)
