Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
search anomalies involving the new urn:x-dc uri formed from dc.relation.ispartof and dc.identifier #4611
Consider two documents A and B:
I annotate both.
I expect results for both from this query but get none:
I do /not/ expect results from this query:
But it returns both.
Clues as to why:
I think the backend assumes dc:identifier is a doi?
The reason this is not working is because the third
The client does this when constructing the fingerprint that is used to search for annotations.
This is an issue, because our code assumes that
That seems good for now, thanks!
I presume it leaves open the possibility that we can later invent a new equivalence type (something like, say, chapter-section), to augment the set of types in document_uri?
The reason for that being, as we've discussed, so that book publishers can coalesce annotations across syndicated copies of works in the same way that scientific publishers now can using DOIs.
Existing document_uri types:
Yes. There are several cases to consider for the value of
I can check, but if you happen to know offhand: if we are not now saving a DOI as the result of parsing dc.relation.ispartof in conjunction with dc.identifier, are we saving that raw data for possible later use? If not, and we do later invent a new equivalence, I suppose we can reconstruct from sources.