-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Congratulations to the contingent from Providence for being selected
by the Code4Lib members as the host site for the next meeting. I'm
looking forward to being at the meeting there next year.
Peter
- - --
Peter Murrayht
The election is over, and Brown University has won a decisive victory to
host Code4Lib 2009 in Providence, RI. Let me be among the first to
congratulate them on their successful proposal. I'm certain we will have a
great conference in 2009 and I look forward to helping them make it so. And
if our p
Worldcat Link Manager will use the last valid (including check digit)
ISBN in the OpenURL, whether in an rft_id or in an rft.isbn. Currently
xISBN is used in the response if it is turned on. Multiple rft_id is
valid according to spec.
On Feb 19, 2008, at 9:26 AM, Ross Singer wrote:
Actually, th
I agree; issn is not an identifier for an article. But in general, a
resolver should be smart enough to know what serial is meant even if a
variant issn is supplied.
I do not agree that it would be helpful for generators to send
multiple issn's. They currently can send issn and eissn; if the
reso
Multiple rft_id's is a fine solution to isbn for a book citation---but if
you've got an article citation, that lives in a particular journal with an
issn, and you know the issn of that journal---please don't put it in a rft_id.
An ISSN is not a good identifier for one particular article IN the
I'm not sure, it seems to me that it could never be harmful, and could
sometimes be helpful, for the CO generator to send all the information it has.
Sure, a good link resolver _should_ be able to resolve any valid ISSN, it
shouldn't need multiple ISSNs. But we all know that 'should' doesn't a
