Difference between revisions of "ESciDoc Transfer Ownership"
Jump to navigation
Jump to search
m (→Resources) |
|||
Line 2: | Line 2: | ||
*for Items | *for Items | ||
*for Containers | *for Containers | ||
*for Contexts | *for Contexts | ||
==Definitions== | ==Definitions== |
Revision as of 12:09, 8 February 2010
Resources[edit]
- for Items
- for Containers
- for Contexts
Definitions[edit]
- Owner of a resource in eSciDoc is a user who has created the resource (the depositor of the resource) i.e. property: created-by
- Transferring of the ownership would mean that another user is from the moment of transferring owner of the resource
Current status[edit]
- Item/Container resources are versioned
- there is no distinction between created-by on resource level and created-by on version level
- only last-modified by on version level is kept for each version
- Context resource is not versioned
- there is only distinction between created-by
Approaches for Items/Containers[edit]
Modify created-by for all versions of the resource[edit]
- this has to be done by special core method
- the information on who had been previous owner is lost
- an entry in the version history shall be made with event-type (transfer ownership) and information on the old user
- new user becomes automatically "created-by" of the resource
- rights and privileges related to the owner automaticaly are transferred to the new owner
- simpler, smaller revision needed
Modify created-by for last version of the resource only[edit]
- core service has to introduce created-by for versions as well
- in this case, created-by for resource will be equal to created-by for versions starting with the version in which the resource was at the time of ownership transfer
- rights and privileges related to the owner are always checked by created-by on the resource level (not on the version)
- complex, huge revision needed
Approaches for Contexts[edit]
- Context related roles are:
- one possible approach is to do nothing, but assume that the user who needs to have "ownership" on the context has Context Modifier role
- another approach