This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Skip to end of metadata
Go to start of metadata

ArcLight is an effort to build a Blacklight-based environment to support discovery (and digital delivery) of information in archives, initiated by Stanford University Libraries.


ArcLight Phase II Work Cycle, August 13-October 11, 2019

Stanford, University of Michigan, Indiana University, Princeton University, and Duke University are collaborating on a second phase of community-based software development on ArcLight. Please see our GitHub repository, our demo videos, or our demo site to see what we're doing!.


Objectives

We began the design process with a few high-level and preliminary objectives for ArcLight:

  • Discovery of physical and digital objects (e.g., finding aids described using EAD, full text search for digital archival materials, presentation and delivery of digital materials)
  • Compatibility with Samvera and ArchivesSpace
  • Developed, enhanced, and maintained by the Samvera/Blacklight community

Process and History

Our project has been community focused from the beginning:

  • 2015-2017: a thorough user-centered design process (2015-2017), with the goal of producing design documentation to guide development
  • April 10-June 2, 2017: development of a minimum viable product (ArcLight MVP) on which to base further development, between Stanford and University of Michigan. See demo videos from this work cycle.
  • August 13-October 11, 2019: continued community-focused development, between Stanford, Duke, Michigan, Indiana, and Princeton

Collaboration and Communication

To better support the relevant objectives of other institutions interested in the solutions ArcLight could provide, we've been collaborating with other institutions during the ArcLight Design Process and the ArcLight MVP work cycle. We expect that development of ArcLight will also involve contributions from multiple institutions. If you're interested in contributing to development or testing ArcLight, please let us know!

Email list: To get updates or communicate with us about ArcLight, please join the ArcLight Google Group (arclight-community@googlegroups.com). 

Slack channel: To communicate with us more informally, please join the #arclight channel on the Code4lib Slack team. If you're not on the Code4lib Slack team, you can request an invitation using this form or by contacting us via the email list. 

Related Resources


  • No labels