Description
#1174 and #1258 have some discussion about the Request button. The team currently working on ArcLight is unlikely to have time to do more than relocate the button as described in #1258, but in the future it might be useful to explore how the requests process could be more fully supported by core ArcLight.
@crugas had some ideas based on UGA's current implementation (some good visual illustrations of the process are in #1174):
It would be great if the requests button could appear based on an institution's own needs - aka dependent on component level requesting per institution. We request things by the box here, so anything that doesn't have a box or equivalent container wouldn't get a request button (like a series, subseries, or collection). Other institutions probably request things by the folder, others by the collection, etc.
Being able to de-duplicate requests would be very important for us and maybe others. If you have a user requesting the same "Box 1" in a collection because they click the "Request" button on every item, that ends up with a lot of unnecessary requests and backend messiness.
Institutions vary a lot in how they handle requests, so I think this topic would require a fair amount of analysis and community discussion, but if feasible, a potential enhancement to the current "Request button and that's it" state of things could benefit the community, since most institutions do have a request process.