Child pages
  • ArcLight Information Architecture: Phase 1
Skip to end of metadata
Go to start of metadata


This phase of the design process has been completed.


Our goal for Phase 1 of the ArcLight information architecture process was to identify the primary types of users and establish a core set of requirements that could be used to inform the design work in later phases of the overall design process for ArcLight. The two primary artifacts developed during this phase were a set of personas, derived from data gathered during user interviews and analyzed further upon their completion, and a set of requirements with a draft prioritization used as the basis for discussion with stakeholders. 


Staff from Stanford University Libraries, University of Michigan, and Georgia Tech developed six personas period:

  • a support developer, responsible for deploying and assisting with the maintenance and customization of an archival discovery system;
  • an (application) administrator, responsible for day to day configuration and maintenance of the application and likely understood as a technically-savvy archivist;
  • an arrangement and description archivist, responsible for publishing and updating archival description;
  • a public service archivist, responsible for reference and instruction;
  • a community researcher, with low to moderate technical proficiency; and
  • an advanced researcher (university faculty member), familiar with public access catalogs, finding aids and online collections.

Discussion with stakeholders at at Stanford University Libraries also led us to identify a set of additional needs for curators, related to both using archival descriptions and materials like subject guides to help present an institution's collections to support their acquisition function, as well as the development of interpretive materials, including online exhibits.


We developed the requirements following the completion of the personas. The requirements were informed by the personas, in addition to in-depth review of the user interview analysis and other stakeholder documents provided to us during  ArcLight Discovery: Phase 1. We prioritized the requirements using the MoSCoW method (Must haveShould haveCould have; and Won't have) to inform the scope of work for an upcoming work cycle led by Stanford to produce a minimum viable product.


Personas



Requirements

#CategorySub-CategoryRequirementPrioritizationDesign Q'sIn Mockups?Source
1.11. Core DiscoveryAccessibilityAccessible (WCAG 2.0 level AA)1 - Must have n/a?Stanford ArcLight feedback
1.21. Core DiscoveryAccessibilitySupport accessibility standards for all researchers1 - Must have n/a?Michigan ArcLight Feedback
1.31. Core DiscoveryBrowseFacet and refine search results1 - Must have YArcLight 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
1.41. Core DiscoveryBrowseFacet and refine search results by agent/creator1 - Must have YArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.51. Core DiscoveryBrowseFacet and refine search results by content types1 - Must haveindexingNArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.61. Core DiscoveryBrowseFacet and refine search results by dates1 - Must haveindexingYArcLight 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
1.71. Core DiscoveryBrowseFacet and refine search results by digital materials1 - 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
1.81. Core DiscoveryBrowseFacet and refine search results by formats1 - Must haveindexingNArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.621. Core DiscoveryBrowseFacet and refine search results by level of description1 - Must haveindexingNArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.91. Core DiscoveryBrowseFacet and refine search results by location/repository/department1 - Must have YArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.111. Core DiscoveryBrowseFacet and refine search results by subject1 - Must have YArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.121. Core DiscoveryBrowseProvide by browse by subject/creator1 - Must haveYNArchivesSpace PUI Report
1.151. Core DiscoveryDiscoveryEmploy multiple search/discovery strategies from finding aids/discovery interface.1 - Must have YArcLight Personas - Experienced researcher
1.171. Core DiscoveryDiscoveryMust accommodate different levels of description1 - Must have YNYU Reqs 27; ArcLight interview analysis
1.201. Core DiscoveryDiscoverySupport for discovery from multiple departments/repositories1 - Must have YNYU Reqs 5; Michigan ArcLight feedback; ArcLight interview analysis
1.211. Core DiscoveryInternationalizationInternationalization-friendly1 - Must haven/aNStanford ArcLight feedback
1.221. Core DiscoveryInternationalizationSupport for multiple languages and diacritics in description1 - Must haveYNArcLight interview analysis
1.231. Core DiscoveryNavigationMove from results inside a finding aid or digitized item metadata to other search and browse options for related collections or through access points1 - Must have NArcLight Personas - Community researcher; NYU Reqs 1; Michigan ArcLight Feedback; ArcLight interview analysis
1.241. Core DiscoveryNavigationOnce in a given collection, browse/navigate the hierarchy of archival description1 - Must have YArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 1; Penn State ArcLight feedback; CHF ArcLight Feedback
1.251. Core DiscoveryNavigationPermit searching and browsing of archival hierarchies/context so users can explore components and also return to parent components/records1 - Must have YMichigan ArcLight Feedback
1.261. Core DiscoveryNavigationView and navigate finding aid components in search results1 - Must have YArcLight Personas - Public service archivist; NYU Reqs 1; ArchivesSpace PUI Report
1.291. Core DiscoverySearchSearch across all collections (or a subset thereof) by keyword (or specific categories, such as names, places, and subjects)1 - Must have YArcLight Personas - Experienced researcher; Penn State ArcLight feedback; Georgia Tech ArcLight feedback; USHMM ArcLight Feedback; Michigan ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements
1.301. Core DiscoverySearchSearch within a specific collection or component by keyword (or specific categories, such as names, places, and subjects)1 - Must have YArcLight Personas - Experienced researcher; NYU Reqs 2; Penn State ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.321. Core DiscoverySEOCollection components have stable URIs1 - Must have n/a?NYU Reqs 5
1.331. Core DiscoverySEOCollections have stable URIs1 - Must have n/a?NYU Reqs 5
1.341. Core DiscoverySEODescription is indexed appropriately by search engines (Google, etc.)1 - Must have n/a?NYU Reqs 20; Michigan ArcLight Feedback; ArcLight interview analysis
1.351. Core DiscoverySEODigital items have stable URIs1 - Must have n/a?ArcLight interview analysis; NYU reqs 5; RAC DAMS requirements
1.361. Core DiscoverySEOEmploy multiple search/discovery strategies outside the finding aids/discovery interface and find relevant results.1 - Must have YArcLight Personas - Community researcher
1.371. Core DiscoverySEORepositories/departments have stable URIs1 - Must have n/a?NYU Reqs 5
1.381. Core DiscoveryUI featuresClear presentation of information regarding access/use restrictions (including copyright)1 - Must have Y (sort of)ArcLight Personas - Experienced researcher
1.411. Core DiscoveryUI featuresDemonstrate ArcLight on large-screen displays in an instructional context1 - Must havevisual designNArcLight Personas - Public service archivist; Georgia Tech ArcLight feedback
1.421. Core DiscoveryUI featuresDiscern original order from display1 - Must have YArcLight interview analysis
1.431. Core DiscoveryUI featuresDisplay breadcrumb for hierarchy for each item/component in a search result1 - Must have YArcLight Personas - Public service archivist; NYU Reqs 7; Penn State ArcLight feedback; Michigan ArcLight Feedback; Yale Kissinger wireframes; ArchivesSpace PUI Report; ArcLight interview analysis
1.631. Core DiscoveryUI featuresDisplay container information for a given component (when available)1 - Must have YColumbia meeting feedback
1.451. Core DiscoveryUI featuresDisplay/link digital material at various levels: item, folder, series, and/or collection1 - Must have YArcLight Personas - Arrangement and description archivist; Indiana ArcLight feedback; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis
1.481. Core DiscoveryUI featuresIcons and/or other visual cues for different formats and levels1 - Must have YNYU Reqs 6; ArchivesSpace PUI Report
1.491. Core DiscoveryUI featuresLeverage / inherit hierarchical data: subjects/creators/rights captured at higher levels of description is displayed "further down"1 - Must haveneeds discussionNNYU Reqs 2; ArcLight interview analysis
1.501. Core DiscoveryUI featuresMobile friendly design1 - Must haveY = responsiveNNYU Reqs 25; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
1.511. Core DiscoveryUI featuresMost users will enter through search engine. Design should consider users coming from this path as well as through our discovery layer1 - Must haveYNNYU Reqs 26
1.521. Core DiscoveryUI featuresPresent 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
1.541. Core DiscoveryUI featuresReceive search results that include (and distinguish between) collections, specific components thereof, and immediately accessible digital content.1 - Must have YArcLight 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
1.551. Core DiscoveryUI featuresResponsive design1 - Must have n/a?Michigan ArcLight Feedback; Georgia Tech Arclight feedback
1.561. Core DiscoveryUI featuresRights info is clear1 - Must have Y (sort of)NYU Reqs 28; ArcLight interview analysis; RAC DAMS requirements
1.571. Core DiscoveryUI featuresUser knows where they are in the hierarchy; easily discover the context of any individual item/component within the hierarchy of the collection1 - Must have YArcLight Personas - Public service archivist; NYU Reqs 7; Penn State ArcLight feedback; Michigan ArcLight Feedback; Yale Kissinger wireframes; ArcLight interview analysis
1.581. Core DiscoveryUI featuresView and navigate the Finding Aid as a complete document1 - Must have YArcLight Personas - Public service archivist; NYU Reqs 1; Penn State ArcLight feedback; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
1.611. Core DiscoveryUI featuresWhen 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 materials1 - Must have YMichigan ArcLight Feedback; ArcLight interview analysis
2.182. User/Request ManagementSaved lists/bookmarksCreate, save, and share selection lists (all users)1 - Must have Y (partially)ArcLight Personas - Public service archivist; RAC DAMS requirements
2.192. User/Request ManagementSaved lists/bookmarksShopping cart-like functionality for saving search results, purchasing digital reproductions of files, or requests1 - Must have YGeorgia Tech ArcLight feedback; Michigan ArcLight Feedback; ArchivesSpace PUI Report; ArcLight interview analysis; RAC DAMS requirements
2.212. User/Request ManagementUI FeaturesInclude contextual information about and identifiers or item/component requested in all views (e.g. for archivists viewing requests, etc.)1 - Must haveYNArcLight interview analysis; RAC DAMS requirements
2.222. User/Request ManagementUI FeaturesNavigate directly to the item/folder/collection referred to in the request1 - Must have n/a?ArcLight Personas - Public service archivist
2.232. User/Request ManagementUI FeaturesReceive 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
2.242. User/Request ManagementUser accountsAbility to create and log into a user account, even though user is not associated with institution1 - Must have NArcLight Personas - Community researcher; Georgia Tech ArcLight feedback; ArcLight interview analysis
2.252. User/Request ManagementUser accountsAllow users to create an account and see notifications and activity-related information.1 - Must have NArcLight Personas - Experienced researcher; Georgia Tech ArcLight feedback
3.13. Indexing/PublicationArchival metadataImport of EAD without relying on ArchivesSpace API1 - Must have n/a?NLM ArcLight feedback
3.23. Indexing/PublicationArchival metadataSupport and recognize EAD elements for search and disambiguation1 - Must have n/a?Michigan ArcLight Feedback
3.33. Indexing/PublicationArchival metadataSupport for EAD20021 - Must have n/a?CHF ArcLight Feedback; ArcLight interview analysis
3.113. Indexing/PublicationDigital object metadataSupport indexing/display of digital object metadata from multiple systems/formats1 - Must have n/a?NYU Reqs 13
3.133. Indexing/PublicationIndexingConfigurable indexing (or weighting/boost rules) to improve relevancy1 - Must have NNYU Reqs 14
3.143. Indexing/PublicationIndexingSupport 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
5.25. System integration/data exportAPI/aggregationAPI to be aggregator-friendly1 - Must have n/a?NYU Reqs 30; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis
5.95. System integration/data exportDigital object deliveryIntegrating with systems that deliver digital content outside of ArcLight1 - Must have YArcLight Personas - Support developer
6.86. Digital objectsIntegrated deliveryDisplay of AV in context of description1 - Must have Y (sort of)NYU Reqs 18; ArcLight interview analysis
6.96. Digital objectsIntegrated deliveryDisplay of images in context of description1 - Must have YNYU Reqs 17; ArcLight interview analysis
6.136. Digital objectsIntegrated deliverySupport for user access to digital content1 - Must have YArcLight Personas - Support developer; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
6.156. Digital objectsUI featuresClearly communicate the level (collection, series, sub-series, item, etc.) of description for digital objects1 - Must have YNYU Reqs 6; Michigan ArcLight Feedback
6.166. Digital objectsUI featuresDisplay 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 display1 - Must have Y (sort of)Michigan ArcLight Feedback
6.196. Digital objectsUI featuresPreview digital content with thumbnails1 - Must have YMichigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements
1.131. Core DiscoveryDiscoveryBring 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
1.161. Core DiscoveryDiscoveryEngaging landing page with featured content2 - Should have YNYU Reqs 3
1.191. Core DiscoveryDiscoverySee an overview of the repository based on highlighted facets or curated themes2 - Should have YArcLight Personas - Public service archivist; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis
1.281. Core DiscoverySearchProvide advanced search, with support for search operators2 - Should have NArchivesSpace PUI report; RAC DAMS requirements
1.391. Core DiscoveryUI featuresCollapsable/expandable levels of description2 - Should have Y (partially)Michigan ArcLight Feedback; CHF ArcLight Feedback
1.401. Core DiscoveryUI featuresContext tree with collapsable/expandable levels of description2 - Should have Y (sort of)Michigan ArcLight Feedback; CHF ArcLight Feedback; Yale Kissinger wireframes; ArchivesSpace PUI Report; ArcLight interview analysis
1.441. Core DiscoveryUI featuresDisplay preferred citation2 - Should have YArchivesSpace PUI Report; ArcLight interview analysis
1.461. Core DiscoveryUI featuresFields within display need to be labeled with understandable language, not archival jargon2 - Should have YNYU Reqs 29
1.471. Core DiscoveryUI featuresHelp manage researcher expectations regarding availability and immediacy of access to physical and digital content2 - Should have Y (partially)Michigan ArcLight Feedback; ArcLight interview analysis
1.531. Core DiscoveryUI featuresProvide multiple views of components (like a file explorer) - detailed view vs icons2 - Should have?? need more infoNMichigan ArcLight Feedback
1.591. Core DiscoveryUI featuresView digital objects in search result as a thumbnail grid2 - Should have?? is this a valid requirement?NArchivesSpace PUI report
1.601. Core DiscoveryUI featuresView/sort box / folder / series in different ways (e.g. sort children of current component)2 - Should have YNYU Reqs 8; Penn State ArcLight feedback; ArcLight interview analysis
2.102. User/Request ManagementRequestsArchivist can initiate delivery requests2 - Should haveY - RequestsNArcLight Personas - Public service archivist
2.122. User/Request ManagementRequestsArchivist can initiate requests, and indicate intended use2 - Should haveY - RequestsNArcLight Personas - Public service archivist
2.132. User/Request ManagementRequestsIndependently submit item requests for download or digitization orders.2 - Should have NArcLight Personas - Community researcher; ArcLight interview analysis
2.142. User/Request ManagementRequestsIndependently submit item requests for use in the reading room.2 - Should have NArcLight Personas - Community researcher; ArcLight interview analysis
2.162. User/Request ManagementRequestsUsers can request digitization of items/components2 - Should have NArcLight interview analysis
3.63. Indexing/PublicationArchival metadataUse archival description/data from ArchivesSpace without manually exporting EAD2 - Should have n/a?CHF ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements
3.73. Indexing/PublicationBibliographic metadataBibliographic metadata import and parsing via MARC upload or ILS API2 - Should have n/a?NYU Reqs 12
3.153. Indexing/PublicationPreviewCreate archival description in ArchivesSpace (and Archive-It, Archivematica, etc.?) and easily preview it in ArcLight2 - Should havestaging serverNArcLight Personas - Arrangement and description archivist; CHF ArcLight Feedback; ArcLight interview analysis
3.163. Indexing/PublicationPreviewPreview finding aids before making them public2 - Should havestaging serverNNYU Reqs 9; CHF ArcLight Feedback
3.173. Indexing/PublicationPublicationCreate archival description in ArchivesSpace (and Archive-It, Archivematica, etc.?) and easily publish it in ArcLight2 - Should have n/a?ArcLight Personas - Arrangement and description archivist; CHF ArcLight Feedback; ArcLight interview analysis
3.203. Indexing/PublicationUpdatesPublish or update certain parts of a finding aid, rather than the whole thing2 - Should have n/a?ArcLight Personas - Support developer; ArcLight interview analysis
4.34. Administration/ConfigurationAnalyticsIntegrate multiple analytics trackers/Google Analytics codes2 - Should haveneeds more definitionNNYU Reqs 16
4.44. Administration/ConfigurationCurationCreate an overview of the repository based on highlighted facets or curated themes2 - Should haveYNArcLight Personas - Public service archivist; ArcLight interview analysis
4.74. Administration/ConfigurationIndexingAssociate local metadata field with item source ID2 - Should haveindexingNArcLight Personas - Administrator
4.84. Administration/ConfigurationPublicationGranular permissions for staff (e.g. controlling who can publish vs. can't delete finding aids)2 - Should haveY - admin UINNYU Reqs 15
4.114. Administration/ConfigurationSocial mediaProvide social media sharing links2 - Should have NGeorgia Tech ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis
4.174. Administration/ConfigurationUI configurationAdd support pages with institution policies, contact info, hours, etc2 - Should haveY - admin UINArcLight Personas - Administrator; NYU Reqs 3; Michigan ArcLight Feedback
4.164. Administration/ConfigurationUI configurationCustomize labels, text, tooltips2 - Should haveY - admin UINArcLight Personas - Administrator; Michigan ArcLight Feedback
5.65. System integration/data exportArchivesSpaceConfigure ArchivesSpace integration2 - Should haveneeds more definitionNArcLight Personas - Administrator and Support developer; Penn State ArcLight feedback
5.175. System integration/data exportDiscoveryEasy integration into an existing Blacklight application2 - Should have n/a?USHMM ArcLight Feedback
5.185. System integration/data exportDiscoveryExport user-saved set or search history to citation management tools (e.g. Zotero)2 - Should have NNYU Reqs 23; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
5.215. System integration/data exportIngest/indexingAllow interaction with ArchivesSpace "global repository" (all repositories in a given application instance) or a subset of them2 - Should have n/a?Yale ArcLight feedback
5.225. System integration/data exportIngest/indexingFinding aid delivery tools that ease the administrative overhead of archival metadata2 - Should have n/a?Penn State ArcLight feedback
5.235. System integration/data exportIngest/indexingUpdate archival description in ArchivesSpace and see changes reflected instantly in ArcLight2 - Should have n/a?ArcLight Personas - Arrangement and description archivist; ArcLight interview analysis
5.275. System integration/data exportRepositoryAllow for integration with a Hydra-based repository2 - Should have n/a?NLM ArcLight feedback; Penn State ArcLight feedback; Georgia Tech ArcLight Feedback; CHF ArcLight Feedback
5.285. System integration/data exportRepositoryConfigure repository integration2 - Should haveneeds more definitionn/a?ArcLight Personas - Support developer
5.315. System integration/data exportRepositoryUse ArchivesSpace IDs as lookup between systems2 - Should haveneeds more definitionNYale ArcLight feedback; CHF ArcLight Feedback
6.56. Digital objectsExternal deliveryLinks to access / preview born-digital materials via integrations with other tools - e.g. Quick view plus, Epadd, File browser, emulator, embeddable panes for archived websites2 - Should have YNYU Reqs 19; ArcLight interview analysis
6.106. Digital objectsIntegrated deliveryGain access to digital content in various formats (digitized text/images, sound recordings, moving images, archived website, born-digital office documents, etc.) directly from finding aids/discovery interface.2 - Should have YArcLight Personas - Experienced researcher; Penn State ArcLight feedback; Georgia Tech ArcLight feedback
6.116. Digital objectsIntegrated deliveryIntegrate digital material from different locations or systems (repository, file server, cloud storage, digital exhibit, etc.) outside of ArcLight2 - Should haveneeds more definitionNArcLight Personas - Arrangement and description archivist and Support developer; Penn State ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis
1.101. Core DiscoveryBrowseFacet and refine search results by rights3 - Could have NArcLight Personas - Experienced researcher and Community researcher; NYU Reqs 2; Penn State ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback
1.141. Core DiscoveryDiscoveryEasily integrated and findable with library catalog and/or library website3 - Could have Y (sort of)NYU Reqs 21; Stanford ArcLight feedback
1.181. Core DiscoveryDiscoveryProvide list of recently processed/indexed collections3 - Could have Y (partially)NYU Reqs 2
1.271. Core DiscoverySearchPermit fuzzy searching/approximation so that researchers do not need to know the exact spelling of subjects, names, or other keywords3 - Could have NMichigan ArcLight Feedback
2.12. User/Request ManagementAccess controlsProvide layered/tiered access3 - Could have NArcLight Personas - Support developer
2.22. User/Request ManagementConsent/waiversCustomize online reading room consent form3 - Could have NArcLight Personas - Administrator
2.32. User/Request ManagementConsent/waiversUsers can sign consent form/waiver3 - Could have NArcLight interview analysis
2.42. User/Request ManagementIntegrationSupport requesting from Aeon3 - Could have NNYU Reqs 22; Penn State ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis
2.62. User/Request ManagementReference/contact mechanismMechanism to solicit feedback/suggestions3 - Could have NArcLight interview analysis
2.72. User/Request ManagementReference/contact mechanismReceive reference assistance.3 - Could have NArcLight Personas - Community researcher; ArcLight interview analysis
2.82. User/Request ManagementRequestsAbility to set a specific date and time for a visit.3 - Could have NArcLight Personas - Community researcher
2.92. User/Request ManagementRequestsAbility to track request/order status.3 - Could have NArcLight Personas - Community researcher
2.112. User/Request ManagementRequestsArchivist can initiate digitization requests based on usage patterns or other criteria3 - Could have NArcLight Personas - Public service archivist; ArcLight interview analysis
2.152. User/Request ManagementRequestsPermit patrons to track request/order status for submitted item requests (for use in reading room) and digitization orders3 - Could have NArcLight Personas - Experienced researcher
2.172. User/Request ManagementRequestsView and manage reference requests from ArcLight3 - Could have NArcLight Personas - Public service archivist
2.202. User/Request ManagementSaved lists/bookmarksTool for users to keep track of what they looked3 - Could have Y (sort of)ArcLight interview analysis
2.262. User/Request ManagementUser accountsRegistration for access to restricted materials3 - Could have NArcLight Personas - Support developer; ArcLight interview analysis
3.43. Indexing/PublicationArchival metadataSupport for EAD33 - Could have n/a?CHF ArcLight Feedback; ArcLight interview analysis
3.53. Indexing/PublicationArchival metadataSupport import/indexing of EAC records3 - Could have n/a?NYU Reqs 12; ArcLight Personas - Arrangement and description archivist; NLM ArcLight feedback; Getty ArcLight feedback; ArcLight interview analysis
3.83. Indexing/PublicationCurationSupport for curatorial creation of collection groupings3 - Could have NNYU Reqs 11; ArcLight interview analysis
3.123. Indexing/PublicationFull textFull text indexing of text from digital objects3 - Could have n/a?ArcLight Personas - Experienced researcher; NYU Req 31; Yale ArcLight feedback; Indiana ArcLight feedback; Penn State ArcLight feedback; Michigan ArcLight Feedback
3.213. Indexing/PublicationUpdatesSupport configurable indexing triggers (e.g. when pushing updates from different sources)3 - Could have NIndiana ArcLight feedback
4.14. Administration/ConfigurationAnalyticsArchivist can use usage patterns or other criteria as decision support for digitization3 - Could have NArcLight Personas - Public service archivist
4.24. Administration/ConfigurationAnalyticsArchivist can view analytics and admin information about an item or collection from the discovery UI3 - Could have NArcLight Personas - Public service archivist; Penn State ArcLight feedback; Georgia Tech ArcLight feedback; CHF ArcLight Feedback; RAC DAMS requirements
4.54. Administration/ConfigurationCurationCreate niche views ("Hydra heads") for projects and classes3 - Could have NGeorgia Tech ArcLight feedback
4.64. Administration/ConfigurationIndexingUI to configure indexing/boost3 - Could have NNYU Reqs 14
4.94. Administration/ConfigurationPublicationStaff interface for publication of finding aids (preview and delete)3 - Could have NNYU Reqs 9; ArcLight interview analysis
4.104. Administration/ConfigurationSocial mediaEnable only the social media features institution supports3 - Could have NArcLight Personas - Administrator; Georgia Tech ArcLight feedback
4.124. Administration/ConfigurationSSOConfigure user authentication to enable single sign-on3 - Could have NArcLight Personas - Administrator; RAC DAMS requirements
4.134. Administration/ConfigurationSSOSSO / Library login integration3 - Could have NNYU Reqs 15
4.154. Administration/ConfigurationStaff viewsProvide ‘curatorial’ view (with login credentials) that would give archivists/internal staff access to unpublished items in ArchivesSpace as well as more extensive preservation/technical metadata3 - Could have NMichigan ArcLight Feedback
4.184. Administration/ConfigurationUI configurationCustomize appearance options3 - Could have NArcLight Personas - Administrator
4.194. Administration/ConfigurationUI configurationCustomize feedback form3 - Could have NArcLight Personas - Administrator
4.204. Administration/ConfigurationUI configurationCustomize online reading room consent form3 - Could have NArcLight Personas - Administrator
4.214. Administration/ConfigurationUI configurationCustomize without developer assistance3 - Could have NCHF ArcLight Feedback
4.234. Administration/ConfigurationUI configurationTurn on sensitive information warning3 - Could have NArcLight Personas - Administrator
5.35. System integration/data exportAPI/aggregationAPIs supporting archival discovery functions3 - Could have n/a?NLM ArcLight feedback; Georgia Tech ArcLight feedback
5.45. System integration/data exportAPI/aggregationProvide ability to express finding aids as EAD for data exchange/aggregation or user reuse3 - Could have n/a?Penn State ArcLight feedback; CHF ArcLight Feedback
5.55. System integration/data exportAPI/aggregationSupport OAI-PMH3 - Could have n/a?NYU Reqs 30; Georgia Tech ArcLight feedback
5.75. System integration/data exportArchivesSpaceProvide access to existing ArchivesSpace API to make it easier to pull data into other applications3 - Could have n/a?CHF ArcLight Feedback
5.85. System integration/data exportCurationAllow for integration of Spotlight3 - Could have NStanford ArcLight feedback; Georgia Tech ArcLight feedback
5.125. System integration/data exportDigital object deliveryAccess to technical documentation on embedded viewers3 - Could have n/a?ArcLight Personas - Support developer
5.105. System integration/data exportDigital object deliveryPermit download/export of digital objects for users3 - Could have NArcLight Personas - Experienced researcher; ArcLight interview analysis
5.115. System integration/data exportDigital object deliverySupport for embeddable viewers3 - Could have Y (sort of)ArcLight Personas - Support developer
5.165. System integration/data exportDiscoveryDownload PDF version of finding aid3 - Could have YNYU Reqs 23; CHF ArcLight Feedback; ArcLight interview analysis
5.245. System integration/data exportOPACConfigure OPAC integration3 - Could have NArcLight Personas - Administrator
5.295. System integration/data exportRepositoryLink from Hydra obejcts to components based on ArchivesSpace IDs3 - Could have n/a?CHF ArcLight Feedback
5.325. System integration/data exportRequestsConfigure Aeon integration3 - Could have NArcLight Personas - Administrator and Support developer; Michigan ArcLight Feedback
5.335. System integration/data exportRequestsPermit integration/data exchange with request system (such as Aeon or alternative platform).3 - Could have NArcLight Personas - Experienced researcher; NYU Reqs 23; Michigan ArcLight Feedback; ArcLight interview analysis
6.16. Digital objectsAV streamingAV content streaming3 - Could have NGeorgia Tech ArcLight feedback; ArcLight interview analysis; RAC DAMS requirements
6.36. Digital objectsDownloadSupport download of digital objects (with associated metadata)3 - Could have NNYU Reqs 23; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback; RAC DAMS requirements
6.46. Digital objectsEmbeddable viewersConfigure viewers for rendering digital material within (or one-click-away-from) ArcLight (viewers for a/v, images, transcripts, side-by-side comparisons, page-turners, WARCs, disk images, email, emulations, etc.)3 - Could have NArcLight Personas - Arrangement and description archivist
6.66. Digital objectsFull text indexingProvide users with the ability to search within digital material (full-text search), not just within description of digital material3 - Could have NArcLight Personas - Arrangement and description archivist
6.76. Digital objectsIntegrated deliveryAccess/present metadata and links from web archives directly or via ArchivesSpace3 - Could have NMichigan ArcLight Feedback
6.126. Digital objectsIntegrated deliveryPermit in-browser viewing/rendering of digital content (as possible) or options to either open an alternative platform in a new browser tab or to download content to render locally.3 - Could have NArcLight Personas - Experienced researcher; Yale ArcLight feedback; Georgia Tech ArcLight feedback; USHMM ArcLight Feedback; Michigan ArcLight Feedback
6.176. Digital objectsUI featuresDisplay/list all formats or versions of a digital objects3 - Could have NArcLight interview analysis
6.186. Digital objectsUI featuresFor complex digital objects, display files/groups of content/archival components in a meaningful way. Allow researchers to view all the files in a folder without (or files in a finding aid) without having to go back and forth to the finding aid.3 - Could have NMichigan ArcLight Feedback
6.206. Digital objectsUI featuresProvide a page turner/viewer3 - Could have Y (sort of)ArcLight interview analysis
6.216. Digital objectsUI featuresProvide comparison/simultaneous viewing of two digital items3 - Could have Y (sort of)ArcLight interview analysis
7.37. Access controlsDeliverySupport and recognize PREMIS rights and conditions governing access/use3 - Could have NMichigan ArcLight Feedback
7.47. Access controlsDescriptionDefine user group(s) that can access items, folders, series, and/or collections (location-based, authentication-based, time-period-based, system-based, etc.)3 - Could have NArcLight Personas - Arrangement and description archivist; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
7.57. Access controlsDiscoverabilityDefine/set discoverability levels (download, streaming, in-person access, remote access, etc.)3 - Could have NArcLight Personas - Arrangement and description archivist; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
7.67. Access controlsDiscoverabilityInclude some sort of authentication layer to restrict the search/display of metadata and/or transcriptions for restricted materials3 - Could have NYale ArcLight feedback
7.77. Access controlsDiscoverabilitySet discoverability at item, folder, series, and/or collection level3 - Could have NArcLight Personas - Arrangement and description archivist; Georgia Tech ArcLight feedback; Michigan ArcLight Feedback
7.87. Access controlsEmbargoSet embargo at item, folder, series, and/or collection level3 - Could have NArcLight Personas - Arrangement and description archivist; Michigan ArcLight Feedback; ArcLight interview analysis; RAC DAMS requirements
7.107. Access controlsUsers and groupsProvide appropriate levels of access to defined user groups: donors, members of a class, university affiliates, etc.3 - Could have NMichigan ArcLight Feedback; RAC DAMS requirements
8.58. Authorities/Linked DataAuthority controlAutomate assignment of authority IDs/URIs3 - Could have NArcLight interview analysis
8.48. Authorities/Linked DataAuthority controlSupport persistent URLs/identifiers for creators (e.g. ORCID)3 - Could have NGeorgia Tech ArcLight feedback
9.69. Enhanced discovery, visualizations, & contributionsCurationProvide support for creator-curated collections/exhibits/etc3 - Could have NGeorgia Tech ArcLight feedback; RAC DAMS requirements
9.79. Enhanced discovery, visualizations, & contributionsCurationProvide support for user-curated collections/exhibits/etc3 - Could have NGeorgia Tech ArcLight feedback; RAC DAMS requirements
1.311. Core DiscoverySearchSearch by tags and user-contributed metadata4 - Won't have NRAC DAMS requirements
2.52. User/Request ManagementIntegrationSupport requesting from Primo4 - Won't have NGetty ArcLight Goals
3.93. Indexing/PublicationDigital object indexingStaff can upload on-demand scans (connection w/ Aeon workflows; syncing to or from ArchivesSpace)4 - Won't have NNYU Reqs 10; ArcLight interview analysis
3.103. Indexing/PublicationDigital object metadataIndex and search technical/preservation metadata from Archivematica4 - Won't have NMichigan ArcLight Feedback
3.183. Indexing/PublicationPublicationGenerate EAC and linked-data-compliant EAD3 via ArchivesSpace or another system/process and publish it via ArcLight to easily create network graphs, visualizations, and linked data sources (across and among items, folders, series, collections, repositories, institutions, and/or organizations)4 - Won't have NArcLight Personas - Arrangement and description archivist
3.193. Indexing/PublicationUpdatesAuto publication of materials where restrictions have expired4 - Won't have NNYU Reqs 9; RAC DAMS requirements
3.223. Indexing/PublicationVersion controlVersion control of content4 - Won't have NGeorgia Tech ArcLight feedback
4.144. Administration/ConfigurationStaff viewsFacilitate management of content via curatorial view, such as initiating additional preservation events4 - Won't have NMichigan ArcLight Feedback
4.224. Administration/ConfigurationUI configurationPull hours from central source when possible4 - Won't have NNYU Reqs 3
5.15. System integration/data exportAnalyticsExport analytics data to other platforms (e.g. Tableau)4 - Won't have NNYU Reqs 16
5.135. System integration/data exportDigital object deliveryExpose viewers to other applications (e.g. ArchivesSpace PUI)4 - Won't have NYale ArcLight feedback
5.145. System integration/data exportDiscoveryAllow integration with ArchivesSpace public UI4 - Won't have NYale ArcLight feedback
5.155. System integration/data exportDiscoveryDiscovery integrated with SearchWorks4 - Won't have NStanford ArcLight feedback
5.195. System integration/data exportDiscoveryIntegrate search from other sources (e.g. local catalog and HathiTrust)4 - Won't have NMichigan ArcLight Feedback
5.205. System integration/data exportDiscoveryIntegrate with Tropy research photo management4 - Won't have NNYU Reqs 23
5.255. System integration/data exportReferenceEasily integrated with chat reference applications (e.g. Libraryh3lp)4 - Won't have NNYU Reqs 24
5.265. System integration/data exportRepositoryAllow for integration of Hyku4 - Won't have NHybox requirements
5.305. System integration/data exportRepositoryShare data from ArchivesSpace to Hydra4 - Won't have NCHF ArcLight Feedback
6.26. Digital objectsAV streamingStream AV side-by-side with a transcript (e.g. oral histories)4 - Won't have NArcLight interview analysis
6.146. Digital objectsStorageSome non-networked dark storage4 - Won't have NGeorgia Tech ArcLight feedback
7.17. Access controlsDeliveryProvide "virtual reading room" access to authenticated users for materials with access/use restrictions.4 - Won't have NArcLight Personas - Experienced researcher; Georgia Tech ArcLight feedback; RAC DAMS requirements
7.27. Access controlsDeliveryRestrict access to digital objects by IP4 - Won't have NNYU Reqs 17, 18, 19; RAC DAMS requirements
7.97. Access controlsStorageSystem storage must have various levels of security4 - Won't have NGeorgia Tech ArcLight feedback; ArcLight interview analysis
8.38. Authorities/Linked DataAuthority controlDefined relationship with SNAC project4 - Won't have NNLM ArcLight feedback; Getty ArcLight feedback; ArcLight interview analysis
8.28. Authorities/Linked DataLinked dataSupport for linked data/RDF4 - Won't have NNLM ArcLight feedback; Getty ArcLight feedback; Stanford ArcLight feedback; Michigan ArcLight Feedback; CHF ArcLight Feedback; ArcLight interview analysis
8.18. Authorities/Linked DataPublicationPublish EAD/EAC-CPF via ArcLight to easily create network graphs, visualizations, and linked data sources (across and among items, folders, series, collections, repositories, institutions, and/or organizations)4 - Won't have NArcLight Personas - Arrangement and description archivist; NLM ArcLight feedback; Getty ArcLight feedback; ArcLight interview analysis
9.19. Enhanced discovery, visualizations, & contributionsAutomated description/analysisConfigure automated description and discovery feature4 - Won't have NArcLight Personas - Administrator; ArcLight interview analysis
9.29. Enhanced discovery, visualizations, & contributionsAutomated description/analysisConfigure entity extraction4 - Won't have NArcLight Personas - Administrator; ArcLight interview analysis
9.39. Enhanced discovery, visualizations, & contributionsCrowdsourcingModerate user-contributed description4 - Won't have NArcLight Personas - Arrangement and description archivist
9.49. Enhanced discovery, visualizations, & contributionsCrowdsourcingSupport entry and integration of user-contributed metadata4 - Won't have NGeorgia Tech ArcLight feedback
9.59. Enhanced discovery, visualizations, & contributionsCrowdsourcingSupport for crowdsourced description4 - Won't have NArcLight interview analysis
9.89. Enhanced discovery, visualizations, & contributionsCurationStable URI for user created collections4 - Won't have NRAC DAMS requirements
9.99. Enhanced discovery, visualizations, & contributionsDeliveryIntegrate "virtual research environment" tools/capabilities4 - Won't have NNLM ArcLight feedback
9.109. Enhanced discovery, visualizations, & contributionsFull text searchFull-text search of applicable born-digital archives as well as digitized materials with OCR.4 - Won't have NArcLight Personas - Experienced researcher; NYU Req 31; Yale ArcLight feedback; Indiana ArcLight feedback; Penn State ArcLight feedback; Michigan ArcLight Feedback; ArcLight interview analysis
9.119. Enhanced discovery, visualizations, & contributionsMultiple presentationsCreate one archival arrangement in ArchivesSpace and set that arrangement to publish in multiple ways in ArcLight (creator's original arrangement, chronological, alphabetical, thematic, user-created arrangement, etc.)4 - Won't have NArcLight Personas - Arrangement and description archivist
9.129. Enhanced discovery, visualizations, & contributionsRecommendationsRecommender engine4 - Won't have NNYU Reqs 32
9.139. Enhanced discovery, visualizations, & contributionsUser data analysisSupport data reuse by enabling users and archivists to perform analysis on data4 - Won't have NGeorgia Tech ArcLight feedback
9.149. Enhanced discovery, visualizations, & contributionsVisualizationsCollection holdings visualizations4 - Won't have NNYU Reqs 33; Georgia Tech ArcLight feedback
9.159. Enhanced discovery, visualizations, & contributionsVisualizationsEasily create network graphs, visualizations, and linked data sources (across and among items, folders, series, collections, repositories, institutions, and/or organizations)4 - Won't have NArcLight Personas - Arrangement and description archivist; NYU Reqs 33; Michigan ArcLight Feedback



  • No labels