exhibits
exhibits copied to clipboard
Better error reporting/handling when importing collections that contain unpublished items
When adding collections to an exhibit from SDR, if the collection includes unpublished items, they will be silently ignored without any indication to the user that they were not imported, and why they were not imported.
Ideally, the process would notify the user of the total number of items in a collection, and how many unpublished items were skipped, and a reason for why they were skipped.
How can I find an unpublished druid for testing purposes?
Argo? Otherwise maybe @caaster can help when she's back next week.
Here is one druid for the moment -- I am working to find a few more that are in different workflow states: druid:bp264pp3784 – registered status & will stay in this status until at least 29 July 2016
Here are two more druids. These are both in a test collection (I spoke to Lynn about using them -- all ok) -- so their workflow state should stay unchanged for the duration of our current work cycle. druid:ym601hw1660 - in accessioning (described) status & druid:db473ds0563 - unknown status. NOTE: these are valid statuses that I run into a lot when trouble shooting in Argo.
@ggeisler @caaster We discussed this issue today and decided that design is needed when a collection that includes unpublished items is imported. We deprioritized this issue with the assumption that there wouldn't be cycles to get that done. I am splitting off a high-priority issue to handle only the case where a druid (or other string) that is unpublished is plugged into the form.
See the https://github.com/sul-dlss/exhibits/tree/sdr-items-status-mockup branch for a working design mockup. Discussed with @cbeer who will take over from here.
Hi @ggeisler doing some ticket grooming & your link above is dead. Can you assist?
@caaster Nope. That link was to a code branch, not a static mockup. As mentioned in my comment, Chris agreed to take it from there. I can't speak to the status of it since then.