SRG Requirements 3.6.07
- Former user (Deleted)
- Former user (Deleted)
Subject Research Guides need to meet the needs of three relatively distinct user groups.
Librarians:
- Log into the system (user authentication; role recognizied).
- View existing guides.
- Create new guide using templates/specialized editors.
- Modify an existing guide.
Instructors:
- Log into the system (user authentication; role recognizied).
- View existing guides (not associated with a particular course).
- Modify an existing guide according to the class' needs (i.e., delete unnecessary resources, add new objects and descriptive text).
- Create new guide using templates/specialized editors.
- Associate guides with relevant classes according to the class parameters, local policy, access control and workflow.
Students:
- Log into the system (user authentication; role recognizied).
- Access guides associated with their class.
- The guide will describe some basic search strategies and it will explain how to evaluate and select the best sources to meet the requirements of the assignment.
SRG Requirements
 |
Description |
Priority |
|---|---|---|
1. |
Subject Research Guides are a part of Sakai/Sakaibrary. |
High |
2. |
Sakaibrary as a data source. |
High |
3. |
A well-specified interchange format. |
High |
4. |
User authentication/roles recognizied/guides must be secure. |
High |
5. |
Templates/specialized editors for different media/targets (i.e., link to a librarian, link to a book. |
High |
6. |
Store generic information (ISSN) rather than site-specific information (stuff to construct an open URL). |
High |
7. |
Enter a citation. |
High |
8. |
Search for a citation. |
High |
9. |
Select existing citation list item. |
High |
10. |
Select existing citation list (entire list vs. item from list). |
High |
11. |
Link to searchable database. |
High |
12. |
High |
|
13. |
Create canned/constrained search. |
Medium |
14. |
Embed RSS feed. |
Medium |
15. |
Link to arbitrary URL. |
High |
16. |
Link to generic individuals ("a librarian"). |
High |
17. |
Link to titled individuals ("this course's instructor", "subject specialist in biology", etc.). |
High |
18. |
Link to specific individuals ("Bill Dueber"). |
Low |
19. |
Link to locations (a library, academic building, office, etc.). |
Medium |
20. |
Have a single instance of each item that appears in a guide (i.e., reference one link to Proquest vs. everyone makes their own links). |
High |
21. |
Hierarchical in layout. |
Medium |
22. |
Organized by headings/subheadings. |
Medium |
23. |
Provide (optional) description at many levels; Override default description. |
High |
24. |
Major changes in authoring interface invoke warnings. |
Medium |
25. |
Guide reusable across semesters. |
High |
26. |
Create gateways to repurpose all data within the guides (information already stored in SearchTools, the Hours database, Library Staff Directory, etc.). |
Low |
27. |
Links and descriptions remain valid despite changes in the underlying resources' metadata (URL, title, the target library's electronic subscriptions, etc.). |
High |
28. |
Library hours displayed with library links. |
High |
29. |
Printable display available with full guide on a single page. |
High |
30. |
Guides are clearly marked as being a production of the library. |
High |
31. |
Last updated date clearly visible. |
High |
32. |
Linkscan can be used on guides. |
Medium |
33. |
Consistent in look-and-feel and information design. |
High |
34. |
Ability to embed some type of audio files (playing short audio files with instructions on how to search, etc.). |
Medium |
35. |
Allow students to comment on a particular database or citation. |
Medium |