Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Agenda:

  • Check-in
  • AR-1300's effects on the staff side
  • next meeting on Nov 1/2?
  • anything else?


Minutes:

present:

  • susan
  • melissa
  • payten
  • james
  • mark t.
  • mark c.
Updates:
  • HM updated the test corpus with the “YNHSC” repo from the training database. 
  • Bobbi has made some more updates to the PUI (some fixes for record counts, and the addition of new icons), and will be back to work on Wednesday. 
  • usability testing update: card sorting exercises were conducted, and the results will be posted to the wiki later this week (or next).
  • accessibility testing: contract signed, and we should have the first set of results in a week or so.
  • indexing fix by HM: making sure that the solr results were updated when for an archival object when a linked digital object is edited, etc.
AR-1300
  • Given that the system will only inherit "missing elements", if there’s at least one element of the same type provided at a lower-level component then the act of inheritance is overridden for that element type. e.g. if you set geographic subjects to inherit as per REQ 2, then they would all inherit from there on down unless you attach a geographic subject at a lower level of description; in that case, only the geographic subject(s) directly attached will display with that component.
  • The only major impact that AR-1300 should have on the Staff UI is the addition of a new option to preview a component with any inherited elements.
  • Configuration options (e.g. as per Req 2) should be handled in a config file with the first release of this new feature. The configuration options should also be application specific, rather than repository specific, as hinted at in the specification.
Next call:
Nov 1, Tuesday, 5 p.m. EST.
  • No labels