search

NationalMuseumAustralia / Collection-API

The public web API of the National Museum of Australia
10 stars 0 forks source link

Related object ID/URL #82

Open f27wood opened 5 years ago

f27wood commented 5 years ago

For the related objects, the Dc has the irn as the ID and linked art has the url. They should be consistent. I am thinking that the URL is most useful, if the DC can be changed to a URL? (If you agree).

Example from object: 75838 Grecian design metal urn and lid

DC "relation" : [ { "id" : "75839", "type" : "object", "title" : "Grecian design metal urn and lid" } ],

LA "related" : { "id" : "http:\/\/csapi-test.nma.gov.au\/object\/75839#", "type" : "PhysicalObject", "label" : "Grecian design metal urn and lid" },

f27wood commented 5 years ago

Hmm actually.. I was thinking the url was to CE but it isn't - duh! So maybe use the irn.

Or is this a non issue as LA adds the url wheras dc doesn't.. and it is OK if they are different..?

staplegun commented 5 years ago

The ID means slightly different things in each format.

The IRI in Linked Data (JSON-LD) is known to be both an identifier, but can can also be followed/resolved to receiving back data. This data received back will probably be Linked Data, so doesn't make sense when you are working with the simple format.

We are thinking of adding href fields in the simple format. These will look the same but it's clearer that they are API links. eg.

{
 "id" : "75839",
 "type" : "object",
 "title" : "Grecian design metal urn and lid",
 "href" : "http://csapi-test.nma.gov.au/object/75839"
}
f27wood commented 5 years ago

Ah okays that makes sense, and good idea about adding hrefs to simple format.