Scenarios

Scenario 3: Updates to repository

Some repository access will involve changes to the content of the repository, for example:  deposit of an object;  editorial activities such as modification of an object’s metadata  annotation of an object;  administrative and maintenance activities. The question arises: in such a case, is it important for repository managers to be able to determine who carried out the action at a later date? This would place requirements ...more »

Submitted by (@neiljacobs)
4 comments

Voting

3 votes
Active

Scenarios

Scenario 2B: Agreements required by resources owners

A similar use case to 2A is where a resource’s owner has attached additional conditions around accessing/using a resource, and individual users must agree to a licence before they are granted access. For example, users may be obliged to agree to use a resource only for educational or non-profit purposes, or to observe copyright This can be implemented using eduPersonTargetedID; that is, this attribute can be used to ...more »

Submitted by (@neiljacobs)
4 comments

Voting

3 votes
Active

Scenarios

Scenario 5: Personal identity management

Note: this case is not itself a scenario, but rather a common theme extracted from the scenarios above. The previous two examples consideration raise the issue of identity management, which is intimately connected with the FAM requirements for some of the use cases, in particular those that involve a long duration in some way. The current approach in the UK federation addresses identity only for relatively short durations, ...more »

Submitted by (@neiljacobs)
3 comments

Voting

5 votes
Active