Re: [dspace-tech] DSpace 6.4 : Metadata based permission
On Fri, Mar 24, 2023 at 11:52:42AM -0700, Arunendra MB wrote: > I have never used Curation task earlier. But is it possible, from the Admin > UI-> Curation Task to execute what you have suggested?If so, a bit more > information would help. > Because I am not a Java programmer. The task that I postulated does not exist. Someone would have to write it. Once the task exists, it could be run from the UI (or the command line). But it might be better to attach it to a workflow so that it runs automatically on new submissions to specific collections. > On Friday, March 24, 2023 at 7:29:47 PM UTC+5:30 Mark H. Wood wrote: > > > On Fri, Mar 24, 2023 at 01:35:08AM -0700, Arunendra MB wrote: > > > There are multiple collections: Collection A,B,C..., each having its own > > > sets of metadata but only one metadata M in common. > > > The requirement is to give access permission to users based on the value > > of > > > M, i.e, if M=m1, then users U1 will have access to items having m1, if > > > M=m2, the users of group U2 will have access to items having m2 in their > > > metadata. > > > > > > Since, there is no way to create sub-collections m1,m2,m3, how can this > > be > > > purpose achieved? > > > > DSpace isn't going to look at your metadata to determine access > > rights. Rights are granted using 'ResourcePolicy's. You need to assign > > different policy sets to the items having M=m1, M=m2, M=m3. This can > > be done: > > > > o manually during ingestion, if the collections have workflow enabled. > > o manually by an administrator after submission is complete. > > o during batch ingestion with SAF, by specifying PERMISSIONS in > > the 'contents' file. (This applies to bitstreams but not, IIRC, to > > the item as a whole.) > > o using a tool (such as a curation task) to examine items in the > > collection and adjust their policy sets based on the value of M. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/ZCGdahcgGHvvurEZ%40IUPUI.Edu. signature.asc Description: PGP signature
Re: [dspace-tech] DSpace 6.4 : Metadata based permission
I have never used Curation task earlier. But is it possible, from the Admin UI-> Curation Task to execute what you have suggested?If so, a bit more information would help. Because I am not a Java programmer. On Friday, March 24, 2023 at 7:29:47 PM UTC+5:30 Mark H. Wood wrote: > On Fri, Mar 24, 2023 at 01:35:08AM -0700, Arunendra MB wrote: > > There are multiple collections: Collection A,B,C..., each having its own > > sets of metadata but only one metadata M in common. > > The requirement is to give access permission to users based on the value > of > > M, i.e, if M=m1, then users U1 will have access to items having m1, if > > M=m2, the users of group U2 will have access to items having m2 in their > > metadata. > > > > Since, there is no way to create sub-collections m1,m2,m3, how can this > be > > purpose achieved? > > DSpace isn't going to look at your metadata to determine access > rights. Rights are granted using 'ResourcePolicy's. You need to assign > different policy sets to the items having M=m1, M=m2, M=m3. This can > be done: > > o manually during ingestion, if the collections have workflow enabled. > o manually by an administrator after submission is complete. > o during batch ingestion with SAF, by specifying PERMISSIONS in > the 'contents' file. (This applies to bitstreams but not, IIRC, to > the item as a whole.) > o using a tool (such as a curation task) to examine items in the > collection and adjust their policy sets based on the value of M. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 <(317)%20274-0749> > www.ulib.iupui.edu > -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/f8544c35-ef20-4232-8c1c-52edb81d573an%40googlegroups.com.
Re: [dspace-tech] DSpace 6.4 : Metadata based permission
On Fri, Mar 24, 2023 at 01:35:08AM -0700, Arunendra MB wrote: > There are multiple collections: Collection A,B,C..., each having its own > sets of metadata but only one metadata M in common. > The requirement is to give access permission to users based on the value of > M, i.e, if M=m1, then users U1 will have access to items having m1, if > M=m2, the users of group U2 will have access to items having m2 in their > metadata. > > Since, there is no way to create sub-collections m1,m2,m3, how can this be > purpose achieved? DSpace isn't going to look at your metadata to determine access rights. Rights are granted using 'ResourcePolicy's. You need to assign different policy sets to the items having M=m1, M=m2, M=m3. This can be done: o manually during ingestion, if the collections have workflow enabled. o manually by an administrator after submission is complete. o during batch ingestion with SAF, by specifying PERMISSIONS in the 'contents' file. (This applies to bitstreams but not, IIRC, to the item as a whole.) o using a tool (such as a curation task) to examine items in the collection and adjust their policy sets based on the value of M. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/ZB2s0KGo%2BD1oI96y%40IUPUI.Edu. signature.asc Description: PGP signature
[dspace-tech] DSpace 6.4 : Metadata based permission
There are multiple collections: Collection A,B,C..., each having its own sets of metadata but only one metadata M in common. The requirement is to give access permission to users based on the value of M, i.e, if M=m1, then users U1 will have access to items having m1, if M=m2, the users of group U2 will have access to items having m2 in their metadata. Since, there is no way to create sub-collections m1,m2,m3, how can this be purpose achieved? -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/69518104-da60-40bd-ab72-b58fc091c09an%40googlegroups.com.
