Description | Requirements
| Item | Overall Progress | Priority | Developer | Description | Dependencies | Comments |
|---|---|---|---|---|---|---|
| User Authentication | ||||||
| Infrastructure | ||||||
 | TBA | Provide connection to local universities authentication system (e.g. Shibboleth at Cornell) | Authentication service provided by university. | |||
| TBA | Establish means for submitting credentials to authentication system | ||||
| TBA | Establish means for getting confirmation from authentication system that user is authenticated and id to use for this user in local applications | ||||
| Model | ||||||
| TBA | Concept of a user. | Should any information about users be stored in the triple store? If so, what is the ontology to use for modeling user information in triples? | |||
| TBA | Establish database table to hold Globally Unique User ID (i.e., from university authentication system), and additional information, such as roles and group membership. | ||||
| User Interface | ||||||
| TBA | Create login widget for use in applications? OR Establish forward and return protocol to local university's login page. | ||||
| Roles | ||||||
| Infrastructure | ||||||
| TBA | |||||
| Model | ||||||
| TBA | Establish database table to hold definitions of Roles (e.g. Role ID, Role Name, Role Description). | ||||
| User Interface | ||||||
| TBA | UI for CRUD for Roles. | ||||
| TBA | UI for assigning role(s) to a specific user. | ||||
| TBA | UI for selecting users for a specific role. | ||||
| Ownership | ||||||
| Infrastructure | ||||||
| TBA | |||||
| Model | ||||||
| TBA | |||||
| User Interface | ||||||
| TBA | |||||
| Group Membership | ||||||
| Infrastructure | ||||||
| TBA | |||||
| Model | ||||||
| TBA | |||||
| User Interface | ||||||
| TBA | |||||
| Collection Viewing | ||||||
| Infrastructure | ||||||
| Lynette R. (Cornell) | |||||
| Model | ||||||
| Lynette R. (Cornell) | |||||
| User Interface | ||||||
| Lynette R. (Cornell) | |||||
