| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | ID | Who [Emory-oriented roles/profiles] | What | Why | EUL Notes | PAWG notes | EUL Priority | ||||||||||||||||||||
2 | EUL1 | As an EUL Collection Manager | I want to assign a primary Library collection affiliation for a work, but be able to control its use in an Exhibition collection that might include works from other Library Collections | so that its source context is not lost if it is added to a user created or exhibit collection and so that I can manage permissions at the Collection-level | Clarify Hyrax Collection Manager role vs. Admin Set functionality and any changes re: Collection Extensions work. | High | |||||||||||||||||||||
3 | EUL2 | As an EUL Collection Manager | I want permissions to be assigned at the top level of a Collection and cascade down to child works, but be override-able at lower levels if needed | so that it is faster for me to assign permissions to appropriate internal staff users on a collection by collection basis | Clarify Admin Set capabilities and their 1:1 workflow constraints. In an environment which will have hundreds/thousands of digital collections, will want to be able to assign/manage permissions at the collection level, but it seems as though this currently happens at the admin set level or work level. We will also have a smaller number of IR "meta-collections" (ETDs, Open Access, Research Data) which may be handled more easily via current Admin Set capabilities. | High | |||||||||||||||||||||
4 | EUL3 | As an EUL Repo Admin | I want to assign permissions at the top level of an entity and have them propagate to their children, but be override-able at lower levels if needed | so that it is faster for me to assign permissions to appropriate internal staff users on a collection by collection basis | Same as above, but a more general principle. Permissions should be inheritable. | High | |||||||||||||||||||||
5 | EUL4 | As a Repository Administrator | I want self-service ability to assign and maintain a set of users within an existing permissions group | so that I don't have to request delevoper assistance or application redeployment to perform routine tasks | I assume this isn't possible through a GUI in Hyrax | Low | |||||||||||||||||||||
6 | EUL5 | As a Repository Administrator | I want self-service ability to create a Group of users that I can assign to various permissions | so that I don't have to request delevoper assistance or application redeployment to perform routine tasks | I assume this isn't possible through a GUI in Hyrax | Medium | |||||||||||||||||||||
7 | EUL6 | As an EUL Collection Manager who manages multiple collections for my Library in a repository shared with multiple business units | I want to manage a subset of groups and users relative to my immediate organization | so that I can more easily manage my Library’s staff permissions without having to request full administrator access to the application | Clarify current Hyrax capabilities. Want to prevent making lots of people full admins just so they can manage multiple containers more easily; don't want to have assign the same users/groups over and over again | Medium | |||||||||||||||||||||
8 | EUL7 | As an EUL Collection Manager/EUL Preservation Curator | I want to restrict editing of selected parts of the digital object's metadata to specialized personnel | so that I can minimize unwanted changes to the object in its preservation state | E.g. student assistants can edit Descriptive Metadata only, but not be able to replace files or modify preservation metadata. Or, we can restrict changes to Rights-related metadata to selected staff only. [I anticipate this will be unlikely to be achieve with metadata in particular (RDF/PCDM)...] | TBD | |||||||||||||||||||||
9 | EUL8 | As an EUL Collection Manager/EUL Preservation Curator | I want to restrict editing of selected parts of the digital object's supplemental preservation files to specialized personnel | so that I can minimize unwanted changes to the object in its preservation state | this many not be a priority but it's a question | TBD | |||||||||||||||||||||
10 | EUL9 | As an EUL Admin Set/Collection Manager | I want to be able to view individual staff/assistants user activity for users modifying objects/files in my collections/dept only | so that I can contact a specific user about their work | Confirm: currently only Admin users only can see user activity? Want to see relevant user activity, not all user activity. Could address this by having Coll Managers contact Admin users for a report | Low | |||||||||||||||||||||
11 | EUL10 | As an EUL Admin Set/Collection Manager | I want to run reports about analytics and inventory that are scoped to my Library or collection hierarchy only | so that I can exclude extraneous data about other Libraries' content and users | Confirm HAWG work and what filters/scope can be applied for administrative structures, and Admin user access only to reports? | Medium | |||||||||||||||||||||
12 | EUL11 | As a Repository Administrator | I want to be able to deselect/select individual abilities assigned to a System Role | so that I can customize default system Roles without requesting developer assistance | E.g. selected Roles are not able to Delete. Having a UI with checkboxes to activate/deactivate pre-set abilities is one approach | Low | |||||||||||||||||||||
13 | EUL12 | As an EUL Collection Manager | I want to constrain the types of Collections that Self Deposit/non-Library users create | so that user-created collections are not competing with Library-curated collections in search and discovery context | Collection Types features assist with this - Collection Creator permission? | Medium | |||||||||||||||||||||
14 | EUL13 | As an EUL Repo Admin | I want to restrict Deletion capabilities to Admins only | because deletion is subject to local policy | May do local customizations to achieve this | High | |||||||||||||||||||||
15 | EUL14 | As an EUL Repo Admin | I want to delineate Library Staff/curating users from self deposit users | so that I can restrict certain system-wide activities to staff only | Self depositors should not be able to see administrative metadata, etc. just because they have an account. Could this be addressed by managing abilities on the Authorized User level? When you sign up you get minimal access, but if you're staff your access can be increased | Medium | |||||||||||||||||||||
16 | |||||||||||||||||||||||||||
17 | |||||||||||||||||||||||||||
18 | |||||||||||||||||||||||||||
19 | |||||||||||||||||||||||||||
20 | |||||||||||||||||||||||||||
21 | |||||||||||||||||||||||||||
22 | |||||||||||||||||||||||||||
23 | |||||||||||||||||||||||||||
24 | |||||||||||||||||||||||||||
25 | |||||||||||||||||||||||||||
26 | |||||||||||||||||||||||||||
27 | |||||||||||||||||||||||||||
28 | |||||||||||||||||||||||||||
29 | |||||||||||||||||||||||||||
30 | |||||||||||||||||||||||||||
31 | |||||||||||||||||||||||||||
32 | |||||||||||||||||||||||||||
33 | |||||||||||||||||||||||||||
34 | |||||||||||||||||||||||||||
35 | |||||||||||||||||||||||||||
36 | |||||||||||||||||||||||||||
37 | |||||||||||||||||||||||||||
38 | |||||||||||||||||||||||||||
39 | |||||||||||||||||||||||||||
40 | |||||||||||||||||||||||||||
41 | |||||||||||||||||||||||||||
42 | |||||||||||||||||||||||||||
43 | |||||||||||||||||||||||||||
44 | |||||||||||||||||||||||||||
45 | |||||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||
47 | |||||||||||||||||||||||||||
48 | |||||||||||||||||||||||||||
49 | |||||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||
51 | |||||||||||||||||||||||||||
52 | |||||||||||||||||||||||||||
53 | |||||||||||||||||||||||||||
54 | |||||||||||||||||||||||||||
55 | |||||||||||||||||||||||||||
56 | |||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||
100 |