Page Comparison

5 min

Roll call and actions from previous meetings

All

Thanks to TAC members for recent listserv contributions:

• Listserv
• Code, documentation and bug reporting

3 discussion questions:

• Request to re-think Instance types
• Should we propose a by-law change?
• Performance when working with AOs with large numbers of direct children

Three discussion questions:

• Request to re-think Instance types
  • We've received a request to re-think how ArchivesSpace handles Instance Types. The rationale is that Instance Types are semantically meaningless (e.g. exports as a top container "label") but potentially misleads users into thinking this it's a place to record format/genre information.
  • Would any sub-teams have interest in looking into this issue further?

• Should we propose a by-law change?
  • By-laws are here: http://www.archivesspace.org/sites/default/files/ArchivesSpace%20Bylaws--Revised%2020160120.pdf
  • Two areas that could be clarified:
    • defining affiliate member and program liaison roles (in Article V Section 4) - see also text e.g. could add text similar to what's been added at bottom of main TAC wiki page:

The Technical Advisory Council also partners and with other community members to help with TAC initiatives. The roles of these other contributors include:  

• Invited affiliate contributors - External contributor with expertise relevant to particular TAC topic and/or task. These members are asked join a particular TAC sub-team for a period of time to help with a specific task, project or work area. These members are added by the Technical Advisory Council Chair and relevant subteam Lead. 
• Program liaison - ArchivesSpace Program staff who work is funded by Membership Fees are encouraged to collaborate with the Councils and join relevant sub-team meetings as a means of ensuring the work of the Program, Council, and community align and are mutually supportive and beneficial. 

• • defining process for handling out of cycle vacancies (in Article V Section 2)
  • Also potentially the bullet in Article V Section 4 that calls out the responsibility of TAC to "review functional enhancements and priorities identified by the Users’ Advisory Council." → but maybe we leave this one for further reflection 

• Listserv discussion re. application performance when working with AOs with large numbers of direct children