Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »



cs-ccs-asm-cm-as


green = works as expected and agreed uponred = does NOT work as expected and agreed uponyellow = unsure




Consensus vs.
Needs Confirmaton

Behavior

Access Role


Works now for Collections

Expected to work
based on description for Collections

Works now for
Admin Sets
Expected to work
based on description for
Admin Sets

Comments
Impacting collections/adminsets


edit_access in solr_doc to collection/adminsetmanagerYESmanager can modify collection metadata

YES

manager can edit the set metadata, participants, and release and visibility settings



depositorNO
NO
NOTE: Creator of the AS does not have edit access at master



viewerNO
NO
NOTE: Creator of the AS does not have edit access at master














read_access in solr doc to collection/adminsetmanagerNO
NO

?
?Should depositors have read access?
I propose an additional setting for sharing that allows this to be ON/OFF for a collection type.

depositorNOdepositor can view the collectionNO

In general...

  • for collections, you likely will want depositors to have read_access.  For example, if a team is jointly curating a collection, depositors to the collection will want to view the collection.
  • for admin_sets, you may not want depositors to have read_access. For example, if you only use the default admin set, you may not want to grant all users access to view that admin set.
X
XI propose that Viewer of admin sets SHOULD have read access.
viewerYESviewer can view the collection even if the visibility permissions of the collection otherwise would not permit them to view it.NO
Rationale...
A user who is granted special access to a collection/admin set have a higher need to be able to see the collection/admin set's metadata and list of works.















access to collection/adminset index via Managed Collections tabmanagerYES
YES
NOTE: Managed Collections does not yet exist at master.
X

If granted read access, depositors will see admin sets in Managed Collections.
depositorYESdepositor can view the collectionNO
Depositors do NOT see admin sets in Managed Collections.

NOTE: Managed Collections does not yet exist at master.
X

If granted read access, viewers will see admin sets in Managed Collections.
viewerYESviewer can view the collection even if the visibility permissions of the collection otherwise would not permit them to view it.NO

Viewers do NOT see admin sets in Managed Collections.

NOTE: Managed Collections does not yet exist at master.


















create collection/adminsetany userSORT OF
ADMINs only
For collections, who can create collections of a particular type is limited to collection type managers and creators.  The admin set collection type also controls who can create admin sets, but the collection type for admin sets is hard coded to only allow admins to do this.














delete collection/adminsetmanagerYESmanager delete the collectionYES

?
?

depositorNO
NO?
Can't see admin sets.  Need to re-test after granting read access.
?
?

viewerNO
NO?
Can't see admin sets.  Need to re-test after granting read access.














access to collection/adminset show pagemanagerYES

YES


via :edit access to the collection
X?
?Need to grant collection/admin set depositor read access to view show page.
depositorNOdepositor can view the collectionNO
PROPOSED change to YES-- via :read access to the collection & admin set
?
?Need to grant admin set viewer read access to view show page.
viewerYES
NO


PROPOSED change to YES for admin sets -- via :read access to the admin set














access to collection/adminset edit pagemanagerYESmanager can modify collection metadataYESmanager can edit the set metadata, participants, and release and visibility settings



depositorNO
NO




viewerNO
NO















add works to collection/adminsetmanagerYESmanager can add to and remove works from the collectionNEW ONLY
admin sets via New Work form only
X
Granting read access will allow depositor to add works from admin show page.
depositorNOdepositor can add works to to the collectionNEW ONLYdepositor can add new works to this administrative set

admin sets via New Work form only

Currently, without read access to collection, a depositor can only add works to a collection via Work → Relationship Tab OR via bulk add to collection on Dashboard → Works index page.

Edit Works → Relationships Tab – DOES NOT include collections where user is depositor, but it SHOULD.

PROPOSED change to grant depositor read access will allow depositors to add works from the collection admin show page.




viewerNO
NO


















remove works from collection/adminsetmanagerYES, IFmanager can add to and remove works from the collection

NO


YES IF requires_membership? false

NO IF requires_membership? true

NOTE: Admin sets uses the master UI which does not surface the ability to remove works from the adminset show page.








depositor?
NO
Can't right now for sure because the depositor can't get to the page where Remove is allowed.

NOTE: Admin sets uses the master UI which does not surface the ability to remove works from the adminset show page.







viewerNO
NO

NOTE: Admin sets uses the master UI which does not surface the ability to remove works from the adminset show page.

















move works between collection/adminsetmanagerYESmanager can add to and remove works from the collectionYES

YES when moving between collections of the same type

YES when moving between different collection types IF requires_membership? false

Minimally, manager has to be a manager/depositor to both collections

NOTE: Move is currently only allowed from edit work Relationships tab, by selecting different collections/admin set.






depositorNO
YES/NO
For admin sets... requires edit access to the work.  Can change for works the depositor created.






viewerNO
NO





Consensus vs.
Needs Confirmaton

Behavior

Access Role


Works now for Collections

Expected to work
based on description for Collections

Works now for
Admin Sets
Expected to work
based on description for
Admin Sets

Comments
Impacting works





edit_access in solr_doc to new worksmanagerYESmanager can edit work metadataYESmanager can edit work metadataApplied at create time when a work is created in just one collection.  Admin set participants are applied every time a work is created.  Collection and admin set permissions are additive.






depositorNO
NO







viewerNO
NO


















read_access in solr doc to collection/adminsetmanagerNO
NO







depositorNOdepositor can view the collectionNO







viewerYESviewer can view it even if the visibility permissions of the collection otherwise would not permit them to view itYESviewer can view works in the set regardless of the visibility settings applied to the workApplied at create time when a work is created in just one collection.  Admin set participants are applied every time a work is created.  Collection and admin set permissions are additive.





All other access to works is based on the edit and read access grants and is controlled by the standard abilities process.


For Admin Sets:

permission_
template_
access
admin set solr docability: can? create_in_adminsetcan access through UI via Dashboard → Administrative Setswork solr doccomments
Definition on participants tab:

Managers of this administrative set can

  • edit the set metadata, participants, and release and visibility settings (via Dashboard → Administrative Sets)
  • edit work metadata (controlled by manager having edit_access on work)
  • add to or remove files from a work (controlled by manager having edit_access on work)
  • add new works to the set

NOTE: Manager is granted access to works and their files only FOR WORKS CREATED AFTER USER BECAME MANAGER

Additional things a manager can do not specifically mentioned in the definition

  • move works to another set where user is manager
  • move works to another set where user is depositor
  • view the admin set through Dashboard → Administrative Sets

  • delete empty admin set (NOT in the definition, but you can do this with edit_access)


Any differences from Collections? (checked if same)

  • edit the collection metadata, sharing, discovery, etc.
  • edit work metadata (works created directly in collection)
  • add to or remove files from a work
  • add new works to the collection


  • move works to another collection where user is manager
  • move works to another collection where user is depositor
  • remove works from collection (not allowed for admin sets)
  • delete empty collection
  • delete collection with works (not allowed for admin sets)
:manage

edit_access

trueYESedit_accessAdmin user creating the admin set is not given edit_access as a user until a manager is added.  This does not have much of an impact as the user is part of the admin group and gets access through that group.

Depositors of this administrative set can

  • can add new works to this administrative set.
:depositN/AtrueNO
Access to works are granted only for works the user creates.

Viewers of this administrative set can

  • view works in the set regardless of the visibility settings applied to the work. For example, viewers can view works in this set even if the works are currently embargoed or restricted.

Additional functionality expected not directly mentioned in the definition

  • view the admin set through Dashboard → Administrative Sets  (NOT in the definition, but QA expected to be able to do this)
:viewN/AfalseNOread_accessThe user is NOT given read access to the admin set and therefore cannot view the admin set through the UI.


For Collections:

permission_
template_
access
definition in UIcollection solr docability: can? create_in_collectionwork solr doccomments
Managers of this collection can
  • add to and remove works from the collection
  • modify collection metadata (including metadata, branding, sharing (to set roles), discovery (aka visibility), relationships (for nesting))
  • delete the collection
:manage

edit_access

trueedit_accessadmin is always a manager
:deposit

Depositors of this collection can

  • view the collection
  • add works to it, even if the visibility permissions of the collecton otherwise would not permit them to view it.
read_accesstrue
access to works are granted only for works the user creates
:view

Viewers of this collection can

  • view it even if the visibility permissions of the collection otherwise would not permit them to view it.
read_accessfalseread_access


NOTE: There is a  difference in definitions and in read_access set on admin_sets and collections for depositors and viewers.  I would propose that Admin Sets use the same behavior as collections.  This change will results in Depositors and Viewers being able to view the admin show page of the admin set AND see them listed in Managed Collections tab in Dashboard → Collections. 

This makes sense for viewers since they must have some special connection with the admin set to be able to see works in it even when they are embargoed or private.  This can make sense for depositors when there are multiple admin sets being used for organization.

My concern is for the special case of a site using a default admin set because they have to.  Users must be able to deposit in it.  In this case, the default admin set is the full set of all works in the repository.  It does not make sense for users to view the show page for that admin set or see it in Managed Collections.


  • No labels