You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the URN:NBN resolver we can get the GPP landing page as weel: http://www.persistent-identifier.nl/ + URN:NBN:NL:IN:20-PGM11475 = https://zoeken.beeldengeluid.nl/program/urn%3Avme%3Adefault%3Aprogram%3A2101608040029283831
We can find the PID in the field nisv.pid: "nisv.pid":{"value":"URN:NBN:NL:IN:20-PGM11475"}
we need to add a mapping for this, so that it is represented in the LOD item.
The text was updated successfully, but these errors were encountered:
@mwigham Recently found out about nisv.pid. It doesn't seem to be listed in our nisv-schema-org-mapping, but it might be in the future. Do you know whether this DAAN payload field is added recently?
The property that we can use for it is: https://schema.org/identifier
could wel be it was added recently, Johannes had to redo the mapping recently for some new fields. It was in any case not present way back when we did the mapping, it's not in the spreadsheet.
Do you think we have any use cases that call for the pid? If so, schema:identifier seems perfect for it.
Do you think we have any use cases that call for the pid?
Not immediately, but I found that the pid acutally refers to the GPP landingpage, that we currently construct ourselves in the beng-lod-server... We could turn to serving the pid instead... but I heard before that not all assets have a pid yet, in which case we still need to construct it.
Using the URN:NBN resolver we can get the GPP landing page as weel:
http://www.persistent-identifier.nl/
+URN:NBN:NL:IN:20-PGM11475
=https://zoeken.beeldengeluid.nl/program/urn%3Avme%3Adefault%3Aprogram%3A2101608040029283831
We can find the PID in the field
nisv.pid
:"nisv.pid":{"value":"URN:NBN:NL:IN:20-PGM11475"}
we need to add a mapping for this, so that it is represented in the LOD item.
The text was updated successfully, but these errors were encountered: