Coins assigns the current absolute_url to the rft.identifier key. This is the key used by Dublin Core Identifier data.
The Coins spec says the URL for the item being described should go in the rft_id key, not rft.identifier. A glance at Zotero's parsing code suggests it looks for URLs in both those places, so moving our automatic url inclusion to rft_id would let us keep the automatic import of the URL, and let users specify an identifier as well (possibly overriding our automatic one) by setting a DC Identifier that's a URL.
Finally, the "automatic" URL isn't one that points to the item, as it should, it's simply the URL for whatever is the current page. On a browse page, this means all items just show the browse page as their "link."
Coins assigns the current absolute_url to the rft.identifier key. This is the key used by Dublin Core Identifier data.
The Coins spec says the URL for the item being described should go in the
rft_idkey, notrft.identifier. A glance at Zotero's parsing code suggests it looks for URLs in both those places, so moving our automatic url inclusion torft_idwould let us keep the automatic import of the URL, and let users specify an identifier as well (possibly overriding our automatic one) by setting a DC Identifier that's a URL.Finally, the "automatic" URL isn't one that points to the item, as it should, it's simply the URL for whatever is the current page. On a browse page, this means all items just show the browse page as their "link."