Kia ora Tim, Thanks for all that information! I did fear it might be an intentional decision for security reasons, because that will rightly make people hesitate to change it too much.
Issue 2413 looks promising to at least cover embargoes – I’ve just added a comment there to note that a solution would need to cover cases where an item might have multiple bitstreams – eg one with an embargo, another one open access, another admin-only, etc – so the label does need to be associated with the bitstream rather than the item as a whole. Being able to divide “restricted” bitstreams between those where the average user can login to access it, and those which are admin-only, is a lot trickier (especially without exposing all the resource policy details via the API) because it needs some way to configure which groups count in which case. I’ll give some more thought to how I might write up a viable feature request for that…. Ngā mihi, Deborah From: DSpace Technical Support <[email protected]> Sent: Thursday, October 5, 2023 4:41 AM To: DSpace Technical Support <[email protected]> Subject: [dspace-tech] Re: Editing display of bitstreams in 7.* based on auth policies Caution: This email originated from outside our organisation. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Deborah, This idea is similar in nature to this feature request to display "access conditions" on the Item page: https://github.com/DSpace/dspace-angular/issues/2413 This would enhance the current "access conditions" feature which can be displayed in search results, etc. See "Item Access Labels" docs: https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration#UserInterfaceConfiguration-ItemAccessLabels However, it's not the exact same as you appear to be wanting to display access status *per bitstream*. That's not yet available in DSpace 7, but it might be thought of in a similar way to these "Item Access Labels". The purpose of those labels is to be able to share *basic access information* on these public pages without sharing every single Bitstream "resource policy" (as sharing all policies could be disclosing too much info, which could be considered a security risk). So, there are concepts in the above links that align with what you want. But, we don't yet have this capability on a bitstream by bitstream level. Tim On Thursday, September 28, 2023 at 7:05:54 PM UTC-5 [email protected]<mailto:[email protected]> wrote: Kia ora, When editing the item view page in a DSpace 5 theme, we could make use of mets “RightsDeclaration” metadata which included rights:Username, listing what individuals/groups had access, and rights:Context, which we could pull auth policy start dates from. This meant we could have bitstreams be listed differently depending on whether they were open-access, login-required, admin-only, or embargoed. Is the same metadata available to the front-end in DSpace 7? I’ve been squinting and furrowing my brow at the Angular code (not my area of expertise…) and I’m starting to get the impression that all it receives from the API is whether or not the file is available to the current logged-in user. Is this accurate? We’re thinking about putting in a request to our host to replicate our old functionality, but it’d be useful to know if that’s something that can be done just by customising the theme, or if it’s something that would require more fundamental changes to the DSpace code first. Ngā mihi, Deborah –––––––––––––––––––––––––––––––––– Deborah Fitchett (she/her) MLIS, RLIANZA Associate University Librarian, Digital Scholarship –––––––––––––––––––––––––––––––––– Learning, Teaching and Library – Te Whare Pūrākau PO Box 85064, Lincoln University Lincoln 7647, Christchurch, New Zealand +64 3 423 0358<tel:+64%203%20423%200358> [email protected] ltl.lincoln.ac.nz<http://ltl.lincoln.ac.nz/> –––––––––––––––––––––––––––––––––– Lincoln University Te Whare Wānaka o Aoraki –––––––––––––––––––––––––––––––––– ________________________________ "The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system." -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/35fc7c72-d206-46ff-ab74-eb73112db9b5n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/35fc7c72-d206-46ff-ab74-eb73112db9b5n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/ME3PR01MB7524C61467410E5EB6B3DEC6C5CBA%40ME3PR01MB7524.ausprd01.prod.outlook.com.
