| A | B | C | D | E | F | G | H | ||
|---|---|---|---|---|---|---|---|---|---|
1 | # | Category | Sub-Category | Requirement | Prioritization | Design Q's | In Mockups? | Source | |
2 | 1.1 | 1. Core Discovery | Accessibility | Accessible (WCAG 2.0 level AA) | 1 - Must have | n/a? | Stanford ArcLight feedback | ||
3 | 1.2 | 1. Core Discovery | Accessibility | Support accessibility standards for all researchers | 1 - Must have | n/a? | Michigan ArcLight Feedback | ||
4 | 1.3 | 1. Core Discovery | Browse | Facet and refine search results | 1 - Must have | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArchivesSpace PUI Report; ArcLight interview analysis; RAC DAMS requirements | ||
5 | 1.4 | 1. Core Discovery | Browse | Facet and refine search results by agent/creator | 1 - Must have | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | ||
6 | 1.5 | 1. Core Discovery | Browse | Facet and refine search results by content types | 1 - Must have | indexing | N | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | |
7 | 1.6 | 1. Core Discovery | Browse | Facet and refine search results by dates | 1 - Must have | indexing | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArchivesSpace PUI Report | |
8 | 1.7 | 1. Core Discovery | Browse | Facet and refine search results by digital materials | 1 - Must have | Y (sort of) | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | ||
9 | 1.8 | 1. Core Discovery | Browse | Facet and refine search results by formats | 1 - Must have | indexing | N | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | |
10 | 1.62 | 1. Core Discovery | Browse | Facet and refine search results by level of description | 1 - Must have | indexing | N | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | |
11 | 1.9 | 1. Core Discovery | Browse | Facet and refine search results by location/repository/department | 1 - Must have | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | ||
12 | 1.11 | 1. Core Discovery | Browse | Facet and refine search results by subject | 1 - Must have | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | ||
13 | 1.12 | 1. Core Discovery | Browse | Provide by browse by subject/creator | 1 - Must have | Y | N | ArchivesSpace PUI Report | |
14 | 1.15 | 1. Core Discovery | Discovery | Employ multiple search/discovery strategies from finding aids/discovery interface. | 1 - Must have | Y | ArcLight Personas - Experienced researcher | ||
15 | 1.17 | 1. Core Discovery | Discovery | Must accommodate different levels of description | 1 - Must have | Y | NYU Reqs 27; ArcLight interview analysis | ||
16 | 1.20 | 1. Core Discovery | Discovery | Support for discovery from multiple departments/repositories | 1 - Must have | Y | NYU Reqs 5; Michigan ArcLight feedback; ArcLight interview analysis | ||
17 | 1.21 | 1. Core Discovery | Internationalization | Internationalization-friendly | 1 - Must have | n/a | N | Stanford ArcLight feedback | |
18 | 1.22 | 1. Core Discovery | Internationalization | Support for multiple languages and diacritics in description | 1 - Must have | Y | N | ArcLight interview analysis | |
19 | 1.23 | 1. Core Discovery | Navigation | Move from results inside a finding aid or digitized item metadata to other search and browse options for related collections or through access points | 1 - Must have | N | ArcLight Personas - Community researcher; NYU Reqs 1; Michigan ArcLight Feedback; ArcLight interview analysis | ||
20 | 1.24 | 1. Core Discovery | Navigation | Once in a given collection, browse/navigate the hierarchy of archival description | 1 - Must have | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 1; Penn State ArcLight feedback; CHF ArcLight Feedback | ||
21 | 1.25 | 1. Core Discovery | Navigation | Permit searching and browsing of archival hierarchies/context so users can explore components and also return to parent components/records | 1 - Must have | Y | Michigan ArcLight Feedback | ||
22 | 1.26 | 1. Core Discovery | Navigation | View and navigate finding aid components in search results | 1 - Must have | Y | ArcLight Personas - Public service archivist; NYU Reqs 1; ArchivesSpace PUI Report | ||
23 | 1.29 | 1. Core Discovery | Search | Search across all collections (or a subset thereof) by keyword (or specific categories, such as names, places, and subjects) | 1 - Must have | Y | ArcLight Personas - Experienced researcher; Penn State ArcLight feedback; Georgia Tech ArcLight feedback; USHMM ArcLight Feedback; Michigan ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements | ||
24 | 1.30 | 1. Core Discovery | Search | Search within a specific collection or component by keyword (or specific categories, such as names, places, and subjects) | 1 - Must have | Y | ArcLight Personas - Experienced researcher; NYU Reqs 2; Penn State ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback | ||
25 | 1.32 | 1. Core Discovery | SEO | Collection components have stable URIs | 1 - Must have | n/a? | NYU Reqs 5 | ||
26 | 1.33 | 1. Core Discovery | SEO | Collections have stable URIs | 1 - Must have | n/a? | NYU Reqs 5 | ||
27 | 1.34 | 1. Core Discovery | SEO | Description is indexed appropriately by search engines (Google, etc.) | 1 - Must have | n/a? | NYU Reqs 20; Michigan ArcLight Feedback; ArcLight interview analysis | ||
28 | 1.35 | 1. Core Discovery | SEO | Digital items have stable URIs | 1 - Must have | n/a? | ArcLight interview analysis; NYU reqs 5; RAC DAMS requirements | ||
29 | 1.36 | 1. Core Discovery | SEO | Employ multiple search/discovery strategies outside the finding aids/discovery interface and find relevant results. | 1 - Must have | Y | ArcLight Personas - Community researcher | ||
30 | 1.37 | 1. Core Discovery | SEO | Repositories/departments have stable URIs | 1 - Must have | n/a? | NYU Reqs 5 | ||
31 | 1.38 | 1. Core Discovery | UI features | Clear presentation of information regarding access/use restrictions (including copyright) | 1 - Must have | Y (sort of) | ArcLight Personas - Experienced researcher | ||
32 | 1.41 | 1. Core Discovery | UI features | Demonstrate ArcLight on large-screen displays in an instructional context | 1 - Must have | visual design | N | ArcLight Personas - Public service archivist; Georgia Tech ArcLight feedback | |
33 | 1.42 | 1. Core Discovery | UI features | Discern original order from display | 1 - Must have | Y | ArcLight interview analysis | ||
34 | 1.43 | 1. Core Discovery | UI features | Display breadcrumb for hierarchy for each item/component in a search result | 1 - Must have | Y | ArcLight Personas - Public service archivist; NYU Reqs 7; Penn State ArcLight feedback; Michigan ArcLight Feedback; Yale Kissinger wireframes; ArchivesSpace PUI Report; ArcLight interview analysis | ||
35 | 1.63 | 1. Core Discovery | UI features | Display container information for a given component (when available) | 1 - Must have | Y | Columbia meeting feedback | ||
36 | 1.45 | 1. Core Discovery | UI features | Display/link digital material at various levels: item, folder, series, and/or collection | 1 - Must have | Y | ArcLight Personas - Arrangement and description archivist; Indiana ArcLight feedback; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis | ||
37 | 1.48 | 1. Core Discovery | UI features | Icons and/or other visual cues for different formats and levels | 1 - Must have | Y | NYU Reqs 6; ArchivesSpace PUI Report | ||
38 | 1.49 | 1. Core Discovery | UI features | Leverage / inherit hierarchical data: subjects/creators/rights captured at higher levels of description is displayed "further down" | 1 - Must have | needs discussion | N | NYU Reqs 2; ArcLight interview analysis | |
39 | 1.50 | 1. Core Discovery | UI features | Mobile friendly design | 1 - Must have | Y = responsive | N | NYU Reqs 25; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback | |
40 | 1.51 | 1. Core Discovery | UI features | Most users will enter through search engine. Design should consider users coming from this path as well as through our discovery layer | 1 - Must have | Y | N | NYU Reqs 26 | |
41 | 1.52 | 1. Core Discovery | UI features | Present users with clear and unambiguous information regarding applicable use or access restrictions that could impact requests or orders. | 1 - Must have | Y (sort of) | ArcLight Personas - Experienced researcher and Community researcher | ||
42 | 1.54 | 1. Core Discovery | UI features | Receive search results that include (and distinguish between) collections, specific components thereof, and immediately accessible digital content. | 1 - Must have | Y | ArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; NLM ArcLight feedback; Penn State ArcLight feedback; Georgia Tech ArcLight feedback; Stanford ArcLight feedback; USHMM ArcLight Feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis | ||
43 | 1.55 | 1. Core Discovery | UI features | Responsive design | 1 - Must have | n/a? | Michigan ArcLight Feedback; Georgia Tech Arclight feedback | ||
44 | 1.56 | 1. Core Discovery | UI features | Rights info is clear | 1 - Must have | Y (sort of) | NYU Reqs 28; ArcLight interview analysis; RAC DAMS requirements | ||
45 | 1.57 | 1. Core Discovery | UI features | User knows where they are in the hierarchy; easily discover the context of any individual item/component within the hierarchy of the collection | 1 - Must have | Y | ArcLight Personas - Public service archivist; NYU Reqs 7; Penn State ArcLight feedback; Michigan ArcLight Feedback; Yale Kissinger wireframes; ArcLight interview analysis | ||
46 | 1.58 | 1. Core Discovery | UI features | View and navigate the Finding Aid as a complete document | 1 - Must have | Y | ArcLight Personas - Public service archivist; NYU Reqs 1; Penn State ArcLight feedback; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback | ||
47 | 1.61 | 1. Core Discovery | UI features | When components of archival collections and digital objects are presented, display a core set of descriptive and administrative metadata (including collection, series, sub-series, item, etc.) to maintain context and provenance of materials | 1 - Must have | Y | Michigan ArcLight Feedback; ArcLight interview analysis | ||
48 | 2.18 | 2. User/Request Management | Saved lists/bookmarks | Create, save, and share selection lists (all users) | 1 - Must have | Y (partially) | ArcLight Personas - Public service archivist; RAC DAMS requirements | ||
49 | 2.19 | 2. User/Request Management | Saved lists/bookmarks | Shopping cart-like functionality for saving search results, purchasing digital reproductions of files, or requests | 1 - Must have | Y | Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; ArchivesSpace PUI Report; ArcLight interview analysis; RAC DAMS requirements | ||
50 | 2.21 | 2. User/Request Management | UI Features | Include contextual information about and identifiers or item/component requested in all views (e.g. for archivists viewing requests, etc.) | 1 - Must have | Y | N | ArcLight interview analysis; RAC DAMS requirements | |
51 | 2.22 | 2. User/Request Management | UI Features | Navigate directly to the item/folder/collection referred to in the request | 1 - Must have | n/a? | ArcLight Personas - Public service archivist | ||
52 | 2.23 | 2. User/Request Management | UI Features | Receive clear and unambiguous information regarding applicable use or access restrictions that could impact his requests. | 1 - Must have | Y (sort of) | ArcLight Personas - Community researcher | ||
53 | 2.24 | 2. User/Request Management | User accounts | Ability to create and log into a user account, even though user is not associated with institution | 1 - Must have | N | ArcLight Personas - Community researcher; Georgia Tech ArcLight feedback; ArcLight interview analysis | ||
54 | 2.25 | 2. User/Request Management | User accounts | Allow users to create an account and see notifications and activity-related information. | 1 - Must have | N | ArcLight Personas - Experienced researcher; Georgia Tech ArcLight feedback | ||
55 | 3.1 | 3. Indexing/Publication | Archival metadata | Import of EAD without relying on ArchivesSpace API | 1 - Must have | n/a? | NLM ArcLight feedback | ||
56 | 3.2 | 3. Indexing/Publication | Archival metadata | Support and recognize EAD elements for search and disambiguation | 1 - Must have | n/a? | Michigan ArcLight Feedback | ||
57 | 3.3 | 3. Indexing/Publication | Archival metadata | Support for EAD2002 | 1 - Must have | n/a? | CHF ArcLight Feedback; ArcLight interview analysis | ||
58 | 3.11 | 3. Indexing/Publication | Digital object metadata | Support indexing/display of digital object metadata from multiple systems/formats | 1 - Must have | n/a? | NYU Reqs 13 | ||
59 | 3.13 | 3. Indexing/Publication | Indexing | Configurable indexing (or weighting/boost rules) to improve relevancy | 1 - Must have | N | NYU Reqs 14 | ||
60 | 3.14 | 3. Indexing/Publication | Indexing | Support indexing/display of archival description from multiple systems/formats (EAD, ArchivesSpace API, spreadsheets, etc.) | 1 - Must have | n/a? | ArcLight Personas - Support developer; NYU Reqs 12; ArcLight interview analysis | ||
61 | 5.2 | 5. System integration/data export | API/aggregation | API to be aggregator-friendly | 1 - Must have | n/a? | NYU Reqs 30; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis | ||
62 | 5.9 | 5. System integration/data export | Digital object delivery | Integrating with systems that deliver digital content outside of ArcLight | 1 - Must have | Y | ArcLight Personas - Support developer | ||
63 | 6.8 | 6. Digital objects | Integrated delivery | Display of AV in context of description | 1 - Must have | Y (sort of) | NYU Reqs 18; ArcLight interview analysis | ||
64 | 6.9 | 6. Digital objects | Integrated delivery | Display of images in context of description | 1 - Must have | Y | NYU Reqs 17; ArcLight interview analysis | ||
65 | 6.13 | 6. Digital objects | Integrated delivery | Support for user access to digital content | 1 - Must have | Y | ArcLight Personas - Support developer; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback | ||
66 | 6.15 | 6. Digital objects | UI features | Clearly communicate the level (collection, series, sub-series, item, etc.) of description for digital objects | 1 - Must have | Y | NYU Reqs 6; Michigan ArcLight Feedback | ||
67 | 6.16 | 6. Digital objects | UI features | Display metadata about the digital object that comes from the archival component (not necessarily the digital object), and does so in a way that allows for a predefined portion or all the metadata to display | 1 - Must have | Y (sort of) | Michigan ArcLight Feedback | ||
68 | 6.19 | 6. Digital objects | UI features | Preview digital content with thumbnails | 1 - Must have | Y | Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements | ||
69 | 1.13 | 1. Core Discovery | Discovery | Bring together elements of the archival collection that might be in different silos (i.e., a Hydra repository, an Archive-It web archives collection, email in ePADD, etc.). | 2 - Should have | Y (sort of) | ArcLight Personas - Experienced researcher; Indiana ArcLight feedback | ||
70 | 1.16 | 1. Core Discovery | Discovery | Engaging landing page with featured content | 2 - Should have | Y | NYU Reqs 3 | ||
71 | 1.19 | 1. Core Discovery | Discovery | See an overview of the repository based on highlighted facets or curated themes | 2 - Should have | Y | ArcLight Personas - Public service archivist; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis | ||
72 | 1.28 | 1. Core Discovery | Search | Provide advanced search, with support for search operators | 2 - Should have | N | ArchivesSpace PUI report; RAC DAMS requirements | ||
73 | 1.39 | 1. Core Discovery | UI features | Collapsable/expandable levels of description | 2 - Should have | Y (partially) | Michigan ArcLight Feedback; CHF ArcLight Feedback | ||
74 | 1.40 | 1. Core Discovery | UI features | Context tree with collapsable/expandable levels of description | 2 - Should have | Y (sort of) | Michigan ArcLight Feedback; CHF ArcLight Feedback; Yale Kissinger wireframes; ArchivesSpace PUI Report; ArcLight interview analysis | ||
75 | 1.44 | 1. Core Discovery | UI features | Display preferred citation | 2 - Should have | Y | ArchivesSpace PUI Report; ArcLight interview analysis | ||
76 | 1.46 | 1. Core Discovery | UI features | Fields within display need to be labeled with understandable language, not archival jargon | 2 - Should have | Y | NYU Reqs 29 | ||
77 | 1.47 | 1. Core Discovery | UI features | Help manage researcher expectations regarding availability and immediacy of access to physical and digital content | 2 - Should have | Y (partially) | Michigan ArcLight Feedback; ArcLight interview analysis | ||
78 | 1.53 | 1. Core Discovery | UI features | Provide multiple views of components (like a file explorer) - detailed view vs icons | 2 - Should have | ?? need more info | N | Michigan ArcLight Feedback | |
79 | 1.59 | 1. Core Discovery | UI features | View digital objects in search result as a thumbnail grid | 2 - Should have | ?? is this a valid requirement? | N | ArchivesSpace PUI report | |
80 | 1.60 | 1. Core Discovery | UI features | View/sort box / folder / series in different ways (e.g. sort children of current component) | 2 - Should have | Y | NYU Reqs 8; Penn State ArcLight feedback; ArcLight interview analysis | ||
81 | 2.10 | 2. User/Request Management | Requests | Archivist can initiate delivery requests | 2 - Should have | Y - Requests | N | ArcLight Personas - Public service archivist | |
82 | 2.12 | 2. User/Request Management | Requests | Archivist can initiate requests, and indicate intended use | 2 - Should have | Y - Requests | N | ArcLight Personas - Public service archivist | |
83 | 2.13 | 2. User/Request Management | Requests | Independently submit item requests for download or digitization orders. | 2 - Should have | N | ArcLight Personas - Community researcher; ArcLight interview analysis | ||
84 | 2.14 | 2. User/Request Management | Requests | Independently submit item requests for use in the reading room. | 2 - Should have | N | ArcLight Personas - Community researcher; ArcLight interview analysis | ||
85 | 2.16 | 2. User/Request Management | Requests | Users can request digitization of items/components | 2 - Should have | N | ArcLight interview analysis | ||
86 | 3.6 | 3. Indexing/Publication | Archival metadata | Use archival description/data from ArchivesSpace without manually exporting EAD | 2 - Should have | n/a? | CHF ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements | ||
87 | 3.7 | 3. Indexing/Publication | Bibliographic metadata | Bibliographic metadata import and parsing via MARC upload or ILS API | 2 - Should have | n/a? | NYU Reqs 12 | ||
88 | 3.15 | 3. Indexing/Publication | Preview | Create archival description in ArchivesSpace (and Archive-It, Archivematica, etc.?) and easily preview it in ArcLight | 2 - Should have | staging server | N | ArcLight Personas - Arrangement and description archivist; CHF ArcLight Feedback; ArcLight interview analysis | |
89 | 3.16 | 3. Indexing/Publication | Preview | Preview finding aids before making them public | 2 - Should have | staging server | N | NYU Reqs 9; CHF ArcLight Feedback | |
90 | 3.17 | 3. Indexing/Publication | Publication | Create archival description in ArchivesSpace (and Archive-It, Archivematica, etc.?) and easily publish it in ArcLight | 2 - Should have | n/a? | ArcLight Personas - Arrangement and description archivist; CHF ArcLight Feedback; ArcLight interview analysis | ||
91 | 3.20 | 3. Indexing/Publication | Updates | Publish or update certain parts of a finding aid, rather than the whole thing | 2 - Should have | n/a? | ArcLight Personas - Support developer; ArcLight interview analysis | ||
92 | 4.3 | 4. Administration/Configuration | Analytics | Integrate multiple analytics trackers/Google Analytics codes | 2 - Should have | needs more definition | N | NYU Reqs 16 | |
93 | 4.4 | 4. Administration/Configuration | Curation | Create an overview of the repository based on highlighted facets or curated themes | 2 - Should have | Y | N | ArcLight Personas - Public service archivist; ArcLight interview analysis | |
94 | 4.7 | 4. Administration/Configuration | Indexing | Associate local metadata field with item source ID | 2 - Should have | indexing | N | ArcLight Personas - Administrator | |
95 | 4.8 | 4. Administration/Configuration | Publication | Granular permissions for staff (e.g. controlling who can publish vs. can't delete finding aids) | 2 - Should have | Y - admin UI | N | NYU Reqs 15 | |
96 | 4.11 | 4. Administration/Configuration | Social media | Provide social media sharing links | 2 - Should have | N | Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis | ||
97 | 4.17 | 4. Administration/Configuration | UI configuration | Add support pages with institution policies, contact info, hours, etc | 2 - Should have | Y - admin UI | N | ArcLight Personas - Administrator; NYU Reqs 3; Michigan ArcLight Feedback | |
98 | 4.16 | 4. Administration/Configuration | UI configuration | Customize labels, text, tooltips | 2 - Should have | Y - admin UI | N | ArcLight Personas - Administrator; Michigan ArcLight Feedback | |
99 | 5.6 | 5. System integration/data export | ArchivesSpace | Configure ArchivesSpace integration | 2 - Should have | needs more definition | N | ArcLight Personas - Administrator and Support developer; Penn State ArcLight feedback | |
100 | 5.17 | 5. System integration/data export | Discovery | Easy integration into an existing Blacklight application | 2 - Should have | n/a? | USHMM ArcLight Feedback |