2016-11-15

Agenda:

• Updates from HM
  • AR-1300
    • In a separate branch right now.
    • ignore the bit about concatenating identifiers with container numbers; mark will add a comment about this to the JIRA ticket.
    • composite identifiers will be a new field in Solr / JSON response.
    • still need to do a test with very-large resources.
    • hoping to merge do the merge this week, so that we can start testing next week.
  • "full tree" vs. 3 up, 3 down, etc.
    • mark and payten did some design work on this.
    • think this will still be doable entirely with Solr, although it's tempting to use to the database (but would be bad if those two were out of synch if using both in the PUI).
  • anything else with Solr?
    • making significant changes to Solr.  when all of this is merged into the core code, there'll be a config option to turn this extra indexing off.
• Updates from Bobbi
  • Ran into a roadblock with the "Not" Boolean feature.  HM will dig into this and try to figure it out.
  • Haven't added to the main branch in a while; working on the "advanced search" features.
  • Not sure if you can add a filter by "repo" feature in the advanced search
    • HM said should be there, so they'll reply to Bobbi about that.  
  • Configurations for "repository" badges, resource tabs, etc.
  • Is there documentation about which files get loaded?  
    • Sounds like Rails is handling of this.  Perhaps there needs to be an initialization / documentation of which config files are read in at start-up time.
• Review first accessibility report
  • lots of feedback about colors and contrast.   Bobbi has asked a few folks at Harvard to provide suggestions on the color ratios, etc.
• Usability updates
  • particularly focused on the repository page update for this call.  we'll need to review some of these as a group for the next meeting.
• Change candidate/beta release date???
  • touch base with Randy once he's back in the office regarding Bobbi's time.
  • next major release of ASpace in March...  next major release after that in June.
  • what about pushing back the candidate release until March-ish, and then committing to getting the production-ready PUI code into the June release?
• Session proposal submitted for code4lib; anyone interested in joining a panel for SAA's annual meeting?
  • James (tentatively) and Susan.
• Next meeting: two weeks from now, same time?
  • November 29th, 4 p.m. EST, 1 p.m. PST, November 30th, 8 a.m. AEST