Difference between revisions of "SUNScholar/Access Control"
Jump to navigation
Jump to search
m |
|||
| Line 8: | Line 8: | ||
''"Access Control" is usually defined as read/write permission for a specified duration, to a particular resource.'' | ''"Access Control" is usually defined as read/write permission for a specified duration, to a particular resource.'' | ||
| − | ==YouTube Videos=== | + | ==YouTube Videos== |
| − | https://www.youtube.com/watch?v= | + | <html5media width="560" height="315">https://www.youtube.com/watch?v=jopOjr2ZblA</html5media> |
| + | |||
| + | <html5media width="560" height="315">https://www.youtube.com/watch?v=rWTWpUDyBg4</html5media> | ||
| − | |||
==Instructions== | ==Instructions== | ||
===[[SUNScholar/Resource_Permissions|For Resource Permissions]]=== | ===[[SUNScholar/Resource_Permissions|For Resource Permissions]]=== | ||
Revision as of 10:08, 20 June 2016
BACK TO OPERATIONAL GUIDE
Introduction
The "resource permissions" feature and the "submit with embargo" feature in the latest versions of DSpace allow you to manage and delegate access control to resources in your repository.
This is not what we want to do in an open access repository, however certain ethical, social, financial and legal realities may prevent this.
"Access Control" is usually defined as read/write permission for a specified duration, to a particular resource.
YouTube Videos
