deternitydx
commented
6 years ago We should put this into place "One option, as I've seen at Wikidata and in OpenRefine, is to store the URI format string, such as "http://lccn.loc.gov/{id}" and then only the ids in the sameAs link." That will also fix issues with URLs changing from http to https.
[the following is a mix of Robbie/Daniel comments/responses. See January 9 email exchange.
The lccn.loc.gov might be the preferred base. Among other things, we should not only have a controlled list, but determine which to the “official” address to persistent ID for each.
Right now, we're simply storing the full URI. One option, as I've seen at Wikidata and in OpenRefine, is to store the URI format string, such as "http://lccn.loc.gov/{id}" and then only the ids in the sameAs link.
I was thinking along these lines. And as I was thinking I understood why Wikidata does it. Economic to manage the external links if the base changes.
In doing that, we could update the formats if the URI changes. With that, I would imagine an interface in which the user chooses an external authority from a list, then the URL format would show up with a text box where the placeholder would appear.
If I understand you correctly, the interface would enable the editor to choose a source, search, select, and the ID would be automatically ingested. If this is how you are thinking, then I was thinking along the same lines. Maybe even enable searching all of them at once? (More complicated! Managing the return list, that is).
Also, I have not given up on the idea that when creating a new SNAC authority record, one search sanctioned sources, find the identity, and automatically initialize a SNAC record with core data from the source. Though related, it adds another layer of complexity. Of course, the source would also need to be available in a form that we could parse and map into SNAC. Each source would need a dedicated map. Just thinking.