[Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap

Custer, Mark mark.custer at yale.edu
Wed Mar 9 10:58:35 EST 2016

Hi, Randy.

A release date has not yet been set for the new PUI, although I'm hopeful that it will be the first major release after the "top container" release.  Right now, we're in the second stage of development for the new PUI, but the next phase has not been mapped out yet, and until that's done I can't say that I'll have a good sense of a release date.

But here's a quick overview of the project so far, with a few highlights in bullet points:

Phase 1 of development, 2015 May - 2015 December:

*         Working group formed

*         Cherry Hill hired with remaining money from the Mellon grant

*         Working group created a group of user personas, which has helped to inform every subsequent step of the project

*         Usability tests conducted at Harvard, Rice, and Yale on current PUI to serve as a baseline for future tests

*         A "test corpus" of finding aids was created so that the new PUI code (to be developed in phase two) could be tested with real-world archival description.

*         Cherry Hill submitted its report and the working group disbanded

Phase 2 of development, 2016 January - 2016 June

*         Brian Hoffman continues development work (which actually started near the end of phase 1)

*         The new PUI code has been merged into the master branch of ArchivesSpace, here: https://github.com/archivesspace/archivesspace/tree/master/public-new

o   The new PUI is not currently packaged with any of the development releases of ArchivesSpace just yet, but Brian Hoffman has provided instructions on how to download the source code and run the new PUI as a development server (if you start with an empty database, you'll also want to open two additional terminal windows, and "./build/run frontend:devserver", to get the staff side running, and "./build/run indexer").

*         The "test corpus" site has been set up by LYRASIS to use the development version of the new PUI in place of the current one, but right now that site is password protected.  Once the development moves further along, and a no crawling directive is adding to a robots.txt file, I hope that the public-side of that site can be opened for everyone to see.  Either way, the new PUI will eventually make its way to a true sandbox, just like we have now at http://public.archivesspace.org for the current PUI.

*         Four members of the former working group have volunteered to do acceptance testing on the PUI JIRA tickets through at least June 30 (thanks Maura Carbone, Cory Nimer, Susan Pyzynski, and Scott Schwartz!)

*         The testing group has finished accepting/rejecting its first round of JIRA tickets for February.  March through June tickets still await, and the tickets that Brian is working on for the rest of this month were identified on Monday (https://archivesspace.atlassian.net/issues/?jql=labels%20%3D%20public_interface%20AND%20Sprint%20%3D%203)

For the rest of phase 2, the testing group will be testing new developments as they're delivered.  Additionally, I'm hopeful that we'll be able to schedule another round of usability tests once the new PUI is fully usable/navigable (i.e. before the UI and underlying metadata is polished, but after a user can search, browse, and view all aspects of the site).

I'm also hopeful that phase 3 will be the start of the release/publicity stage, but it's possible that more development work will still be required by that point to meet all of the features that have been identified as requirements for a minimum viable product for the new PUI.  We should have a much better sense of a timeline for phase 3 in the next couple of months.

As for resources:  at this point, there is only one developer working on the project (you'll see Brian's name assigned to all of those tickets for the March sprint) and five archivists, including myself, who are actively testing and providing feedback about the development.  I should also mention that at Yale we've set aside money to assist in the development of the PUI, so we're planning to contract with a development firm from April - June 30 to work under Brian's lead, contributing directly to the ArchivesSpace core code, to help realize all of the recommendations from Cherry Hill's report as well as to respond to additional feedback during development.  And as Brian notes in the "public new" readme, he's happy for others to contribute (https://github.com/archivesspace/archivesspace/tree/master/public-new#contributing).  If you have other ideas for how the community can contribute, please let us know!

As soon as we know more about a release schedule, we'll follow up with more information.  Also, your email reminds me that I need to get to work on updating the wiki site with information about phase 2, so thanks for that nudge.

All my best,


P.S.  I've been trying to follow ArcLight as much as I can, and I submitted feedback to that project early on.  As far as I'm aware, that project has been put on hold for the time being, but I wouldn't be surprised if it picked back up again soon.  I'll reach out again today, though, to see where they're at in the project.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stern, Randy
Sent: Monday, 07 March, 2016 5:54 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap

Adding to my own email...

I was also wondering if there has been any cross fertilization between the ArchivesSpace public u/I project and the ArcLight concept? If there is to be an open source public u/I project, it would be great to have one instead of two!


From: Stern, Randy
Sent: Monday, March 07, 2016 5:43 PM
To: Archivesspace Users Group
Subject: Public Interface Enhancement Project - Roadmap

Hi all,

What is the best way to get an overview of the roadmap for development of the Public Interface project?

I can see the Cherry Hill report and U/I mockups at http://cherryhill.github.io/aspace_pui/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__cherryhill.github.io_aspace-5Fpui_index.html&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=or4e6voLZHnjL-UqClMvmdhhTeAHbXfK_1zq9g8DF24&s=Dsko5xkOKpBQvUFGvH-LjAzPpTRbbZY3AgkM_khXrK0&e=> and the working group meeting  notes at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_display_ADC_Public-26-2343-3BInterface-26-2343-3BEnhancement-26-2343-3BProject&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=or4e6voLZHnjL-UqClMvmdhhTeAHbXfK_1zq9g8DF24&s=rj34-O5RibItzJ3XVbqFyv0pZKg59EuChUGM77hu3-w&e=>.

But I can't really get a sense of the potential development resources available for the project, a timeline, or a plan for moving forward with development. Is there one that is available for review?

Similarly, information about how the development community might collaborate to move the development forward would be helpful as well.

Thanks for any information you can share.

Randy Stern
Director of Systems Development
Harvard University IT, Library Technology Services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160309/9f120b11/attachment.html>

More information about the Archivesspace_Users_Group mailing list