Date
November 8, 2017 - 2:00pm ET
Call In:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/253264666
or iPhone one-tap:
US: +16699006833,,253264666# or +14086380968,,253264666#
or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 408 638 0968 or +1 646 876 9923
Meeting ID: 253 264 666
International numbers available: https://zoom.us/zoomconference?m=V3mbLzPOeYrz_LnO5BL3k2pgCrJ9eJQ
Attendees:
Not Present:
Goals
Update members on ArchivesSpace program activities including activities of sub-teams
Discussion items
|
|
|
|
| Time | Item | Who | Notes |
Eastern time | Roll Call | Suzanne Stasiulatis | Scheduled Notetaker: Jamie Weeks - Updated Users Advisory Council Main page and UAC Subteams: Descriptions and Rosters page.
|
| Program Update | Christine Di Bella | Notes: New Release: Working on a release to fix some of the items that have recently been reported as bugs. Aim to have this release out later this week, still trying to finish up last minute changes, with a release announcement coming out soon. User Forum: Scouting locations for next year’s user forum in Washington D.C. Also setting up regional location forums for late spring. These will allow similar types of programming for those unable to attend SAA along with some built in social time. More information will be coming in the next couple of months. Webinar: Held a very successful webinar about the new public interface. Ninety logins (some were groups) were in attendance. We plan on having more of these in the coming months. The forum had a mix of technical and non-technical topics. We are open to new ideas for upcoming webinars, please send us your thoughts. Open Call In: Less formal than a webinar, we are going to hold open calls on Zoom with no agenda, where people can call in with questions and share ideas with team members or each other. We are receiving feedback that the listserv is intimidating and some of the topics are on too high of a technical level. This may alleviate some of those concerns. The next call will take place on November 29, 2017. Kim is going to send out announcements about it. Evaluating Code: Setting up a new process where people can go in and provide info on how they are doing things, allowing contributions from users. (Document discussed at the end of the meeting)
|
| Sub-team Reports |
|
|
| Development Prioritization | Jason Loeffler | The sub-team welcomes Megan Blair, Patrick Galligan, and Cory Nimer. Thanks to outgoing member Mark Custer for his contributions. Open issues are distributed as follows: - There are 30 reported bugs in this queue.
- Of these 10 will see resolution in a future major or minor release.
- 4 are awaiting more information from reporters.
- 8 are awaiting prioritization.
- 1 is started.
- 7 are awaiting testing.
- There are 12 new feature requests in this queue.
- Of these 4 will see issuance in a future major or minor release.
- 17 are awaiting prioritization.
- 1 is started.
- 3 are either awaiting more information from reporters or validation by the sub-team.
- Additionally, 5 feature request were deferred to SIEWG for evaluation.
Discussion items for future meetings: Meeting bimonthly (instead of monthly), a system for more transparently tracking the progress of tickets, possibilities for members to vote on issues, and issuing another member survey (similar to last year's survey administered by Brad Westbrook and JL). |
| Documentation | John Zarrillo | - The group is wrapping up peer review of the User Manual.
- It was suggested that we remove and archive documentation of older versions of ArchivesSpace from the User Manual.
- We received documentation on the Assessments module from Adrienne Pruitt at Tufts (who developed the module). We'll test and review the documentation after our next meeting later this month.
- At the same time we'll look at developing documentation for EAD3 exporting.
Notes: User Manual: 75% of the manual has been peer reviewed, we will complete the process before final submission. Archive Documentation: Many newer versions are missing portions and tables of content. Looking into a way to better display them for the archive.
|
| Reports | Carolyn Runyon | - The group welcomed and said goodbye to sziegler (Unlicensed), who is leaving the UAC.
- The group is awaiting feedback from the development team regarding new report definitions, which were developed by the group in March. Once we’ve tested the format and information provided in the report definition for the Shelflist Report, we plan to create a template and develop 38 new pre-defined reports.
- In the meantime, the group is working on a Data Dictionary, which we hope will allow users who wish to create their own custom reports better understand the data stored in ArchivesSpace. Nancy Enneking has been leading the efforts and has produced a rough draft of the Data Dictionary which we are continuing to refine.
|
| Testing | Miloche Kottman | The Testing sub-team added two new members and one member, Max Eckard, resigned so that he can be chair of the Technical Advisory Committee. The current roster of members is: Brittany Newberry, Cory Nimer, Dallas Pillen, Ed Busch, Scott Hanrath, Robert Lay and Miloche Kottman. The sub-team tested ArchivesSpace version 2.2.0 from October 4-10th. This version included 6 bug fixes, the addition of the assessment module and code for the EAD3 exporter. Notes: Cory Nimer and Dallas Pillen are new members of this group. Version 2.2.0: The bugs were fixed, but now the challenge is to test everything else to make sure the new changes didn’t break other things. Testing for the public user interface being added in to this team’s responsibilities. In December 2017, there will be a major release, and they will be testing it for issues and problems.
|
| Other Business |
| Discussion - Program Teams's document ArchivesSpace Process for Evaluating Potential Feature Contributions to the Core Code https://docs.google.com/document/d/1PBLH6FGzvyOF4x1HCnkkL8wnaRfOkcKuEpxfPujTh-8/edit?usp=sharing Christine went through the ArchivesSpace Process for Evaluating Potential Feature Contributions to the Core Code document asking for input and suggestions for each section. Please share this with your technical support team as they can help add necessary information. This is for people who really know code and can add a significant change. This is not to be applied, but just to have input on providing the best possible document to the wider user group in the future. Frequently people have created new developments, they want added to the ArchivesSpace application itself which can be mutually useful to everyone. However, not everything that has been created outside the application is going to be added to the application, it may be something that should be handled differently. There will always be new development work in the program. It allows us to make good thoughtful decisions. These refer to significant changes, with larger feature changes and have done the code themselves or worked with a contractor to do the code for them.
|