Bug #7153
closedMetacatUI doesn't render private archived content correctly
0%
Description
When trying to view a metadata document that has been archived with its direct #view
URL, MetacatUI fails because it only checks to see if the content is in the Solr index. I dont know if this is limited to private content, or if it's the same behavior for public content. Either way, when #view/{pid}
is accessed, we need to 1) query Solr for the record (which we do), then if nothing is found, we need to see if the object is archived via /meta
. If it is, and access is granted, we need to call the view service to render the science metadata.
The data tem interns have been running into this, and so I checked it out with this example:
https://arcticdata.io/catalog/#view/urn:uuid:15b0247a-b681-464f-bed2-9229cc686af8
When passing the token in to /meta
or /view
, getting the system metadata or the XSLT'd content works fine:
curl -H "Authorization: Bearer ${token}" "https://arcticdata.io/metacat/d1/mn/v2/views/metacatui/urn:uuid:15b0247a-b681-464f-bed2-9229cc686af8" and curl -H "Authorization: Bearer ${token}" "https://arcticdata.io/metacat/d1/mn/v2/meta/urn:uuid:15b0247a-b681-464f-bed2-9229cc686af8"
Updated by Lauren Walker about 8 years ago
- Status changed from New to Resolved
The metadata document will be displayed even if archived. MetacatUI will pass the document through the view service and display the rendered metadata. It will also display a warning message that the content is archived.