Table of Contents |
---|
Use case 1
Title (goal) | Fedora managing access conditions |
---|---|
Primary Actor | Librarian/archivist/curator |
Scope | |
Level | User goal |
Story | The producer of Fedora content wants to be able to set access conditions that would allow for the following scenarios:
As for implementation, I can offer some examples of what we use now. We specify the file type/size, the authorization type and then any values associated. Some examples: TIF - Active Directory Group - ManuscriptCurators JPG 600px - IP - list of IP values or ranges PDF - external authentication JPG 1200px - Yale only JPG 150px - open access TIF - NetID - yale\mf438 (or a list of NetIDs) DSK - Active Directory Group - ManuscriptDirectors DSK - Emulation - AppleWin v1.1.8 Basically our need is for very granular levels of permission to be stored with the object in Fedora. Right now it is stored as XML as a data stream, it would be beneficial to have it stored differently so that we could make mass changes to materials for entire collections. Another note, we would only be storing a single JPG or possibly no JPG and only a JP2 and will derive the JPG on the fly. So the access condition setup may include conditions for resolutions of digital formats not contained in the data streams. The JPG examples above would indicate that a single JPG exists as a data stream and from that stream we will derive smaller images. But the access conditions are different for ranges of sizes. For Yale, we stick to these sizes, 150px or less (thumb), 151-600px (medium), 600+ (full resolution). For TIF images we use Full, Half page and Quarter page. Right now, all other sizes/resolutions are tied directly to the file type stored as a data stream. But being able to reference access for something that is dynamically generated would make this scale to future needs. |
...