Open PietroLiuzzo opened 9 years ago
An easy solution (suggested by Bridget Almas) we could be to provide URNs as Perseus does, which would also be nice in terms of what people can do with the data and how they can access it.
We could add a urn with the CTS (Canonical Text Service) structure like the one we use in the EAGLE wiki for data exchange and identification between APIs. This also supports nice citation of inscriptions in digital editions and is very easy to accomplish with the data we have. The structure could be simply the following
http://eagle-network/urn:cts:pdlepi:eagle.tm202331 --> just points to this inscription as identified by Trismegistos id http://eagle-network/urn:cts:pdlepi:eagle.tm202331.perseids-2015-01 --> points to the translation http://eagle-network/urn:cts:pdlepi:eagle.tm202331.edh12345 --> point to instance of edh of a this isncription http://eagle-network/urn:cts:pdlepi:eagle.tm202331.irt1234 --> point to instance of irt of a this isncription http://eagle-network/urn:cts:pdlepi:eagle.idest12345 --> points to another inscription with a different id, this example is a greek inscription ID
This is just a conceptual notion which would facilitate canonical reference to text and could be used with a simple redirect to our API for people who want to use the contents. We could write for example a simple redirect (as it is done in Perseus)
RewriteRule ^/cts/urn:cts:pdlepi:eagle.(.?).(.)$ http://search.eagle.research-infrastructures.eu/solr/EMF-index-cleaned/select?q=entitytype:documental%20AND%20localid:%22$2%22 [P,L]
in the data alongside the TM id and the local id, we could just also print the value of this urn for reference, so
EDR113562 Back to result list | Bibliography | View translations | Original source | Save | Export Content Provider: Epigraphic Database Roma Trismegistos ID: 265360 - http://eagle-network/urn:cts:pdlepi:eagle.tm265360 Content Provider ID: EDR113562 - http://eagle-network/urn:cts:pdlepi:eagle.tm265360.edr113562
Now it is possible to bookmark each page (by clicking on the corresponding link on the left frame). We will consider Bridget Almas's suggestion for the future.
users want to link to content in EAGLE but the urls are never visible so they simply cannot. they could link to the original source but it is not obvious they can do that and they should do that. the original source should probably be specified as something like : LINK TO THIS INSCRIPTION or a field with the surfaced url to the relevant content should be given in the field visualized to the user