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
In IG-curation @roelandordelman mentioned that it was strange that the open dataset doesn't refer to the media suite. In itself it is not part of the asset data, but we can find out whether it is opportune to add a link to the program in the resource viewer. Take note that this is solely about a place (a URL) where (a version of) this resource (program or CreativeWork) can be seen in a portal (MediaSuite) with authorized access (somebody can log in via satosa).
It is not an open landing page as it can be seen in the General public portal. It is also NOT an identifier of the resource (as are the resource identifiers).
For example:
The resource URI: http://data.beeldengeluid.nl/id/program/2102204010337178231 can have a property sdo:mainEntityOfPage, pointing to the landingpage in the MediaSuite: https://mediasuite.clariah.nl/tool/resource-viewer?id=2102204010337178231&cid=daan-catalogue-aggr&st=2102204010337178231
It should be a stable URL though, otherwise data might be corrupted too easily. In that case we would need a PID.
We might have to add an indication that for this page one needs to be authorized, e.g. something like: sdo:RegisterAction, but I am not sure if we would get too much into details when doing that.
For completeness sake: the last part of the URI, even after the catalog type, is the DAAN ID, the part of the resource URI that can be used to uniquely identify this single resource in the resource viewer. It has now only been tested for the example above, so n=1. It is expected that this pattern will be more general.
The text was updated successfully, but these errors were encountered:
In IG-curation @roelandordelman mentioned that it was strange that the open dataset doesn't refer to the media suite. In itself it is not part of the asset data, but we can find out whether it is opportune to add a link to the program in the resource viewer. Take note that this is solely about a place (a URL) where (a version of) this resource (program or CreativeWork) can be seen in a portal (MediaSuite) with authorized access (somebody can log in via satosa).
It is not an open landing page as it can be seen in the General public portal. It is also NOT an identifier of the resource (as are the resource identifiers).
For example:
The resource URI:
http://data.beeldengeluid.nl/id/program/2102204010337178231
can have a property sdo:mainEntityOfPage, pointing to the landingpage in the MediaSuite:https://mediasuite.clariah.nl/tool/resource-viewer?id=2102204010337178231&cid=daan-catalogue-aggr&st=2102204010337178231
It should be a stable URL though, otherwise data might be corrupted too easily. In that case we would need a PID.
We might have to add an indication that for this page one needs to be authorized, e.g. something like: sdo:RegisterAction, but I am not sure if we would get too much into details when doing that.
For completeness sake: the last part of the URI, even after the catalog type, is the DAAN ID, the part of the resource URI that can be used to uniquely identify this single resource in the resource viewer. It has now only been tested for the example above, so n=1. It is expected that this pattern will be more general.
The text was updated successfully, but these errors were encountered: