Agenda
Welcome to Leigh Grinstead, Project Manager!

           
Quick reports on subcommittee activity, with a focus on Minnie's schema compliance work / accomplishments. (20 minutes)

Schema compliance - Minnie --- Edited scripts for going from dtd to schema for UT Alexander Archive, ran a test – it worked but repositories themselves will have to fix some types of errors. Biggest thing will be getting everyone’s mainagencycode (Jennifer Hecker is helping with that) but that’s manageable as we are doing this 1 repository at a time. Now Minnie wants native-schema-compliant XML files to test. Then she will be ready to decide who will go first. Ahead of schedule!  Now ready to contact Rice, A&M and Baylor—to talk to those who talk to those that create in schema already and test the edits in the style sheet. She wants to be sure it works with Native Schema EAD and then wants to do the processing for both together and then which agency will be the first to be converted. It is going smoothly so far. A lot of the files are more standard than she imagined they would be. Going one at a time with each institution helps. She is on track in terms of her timeline. Once her next test is over she will bring in the Native schema compliant files. Which cuts off the need to provide documentation for those who are hand coding.

Amanda says that it wasn’t promised (schema compliance) in the grant but it looks like it may happen during the grant period.

Jennifer – Governance. Added Lisa Struthers as a small repository rep. on the committee. Added info to wiki.

Amy – FundingNot too much to report. No meeting this month, did send a reminder email and to look at look at levels of service and models for sustainability. Leigh did add comments

Becky – Standards – Donna Coates and Becky and Intern Hannah looked at OpenRefine together, at sorting tasks, renaming tasks. Convert xml to json for use in Refine – pare down to high level did not including the container list. Should work if most people have Index Terms in the high level <did> and not in the container list. Working with Minnie on that, phone committee meeting next week.

 Jessica – WebTechs – coming by googledoc link in email

Amanda - Outreach and Education - Amanda has added a page—how do I submit now. Starting from ArchivesSpace, Starting from Archon etc. or HELP—the information will come in October. She will be in contact with Minnie to talk about this.

The committee’s have talked via email and each person has talked with Amanda. UT El Paso is joining now and they are deciding if they want to use proxy encoders to serve as consultants—she has two volunteers. 

Other items to discuss:

• Updates to functional requirements document (Jessica, Amy, Amanda) (5 minutes)

This is currently being refined. Leigh asks if they are weighting the requirements, and discussing them as happening in phases.Kristy Sorensen will be working on this as well.

• Discuss initial steps to create a collection development policy for TARO (all - and this will be due in December) (10 minutes)

Task – gather examples into a google-doc and report at next meeting (Amy & Amanda) This is assigned to the Steering Committee. It seemed like looking at peer institutions, what it looks like—Archives West—RMOA? Etc. maybe the task for this month is to gather examples and report in the next meeting. As far as sharing? Google docs might be preferred so that folks can comment and it isn’t public. Amy and Amanda trade off leading the meetings. Amy can gather and then the meeting will be a little longer in order to discuss the policies more in depth. That will go on the Google Drive dedicated to TARO. There is not an original Collection development Policy that they know of. All the information is in the Admin archives section

• Discuss usability tasks for grant term (all - should we start with "personae" and general tasks, with articulated tasks due end of October?) (10 minutes)
• Leigh commenting that these are very useful to do, and we will be going back to them time and time again. Amy’s idea to get a call out to other TARO members to invite participation, to spare steering committee when all are busy with existing commitments. Steering committee—should they start with a personae model and tasks and articulate those at the end of November? This would be a working meeting again perhaps? Rice has started doing that although they drive people to TARO at this point. They don’t have a lot of money for functional and usability studies so creating these themselves it will be really be important. They think it lays the groundwork to help articulate the platform. Put a call out to the general membership list to get folks to work on this specifically—great idea! They would have to articulate the task clearly but there should be a call before the next meeting and prepare some tasks. That sounds reasonable—there can be a side chat about the timeline for the message and they do have some ideas about what personae they want to test so they aren’t starting from nothing…by the end of October there should be some progress made. Leigh will work Amy and Amanda to set this up

• Creation of ad-hoc usability subcommittee (all to discuss -create committee in October, and members to participate in platform testing thru December) (10 minutes)
• Create a committee in November but they may then test the platforms—that timeline may be shifting because the platform testing is shifting, this will roll into the discussion with Leigh about user personae
• Discuss platform testing & evaluation (Jessica - set to begin in October, go through December) (5 minutes) AtoM will be set up first, and then we will hear more about ArSp

• Make sure all milestones and tasks are documented in Teamwork!