2017-01-23

Owned by Mark Custer
Last updated: Jan 23, 2017
2 min read

Time: 

  • 3 p.m. EST January 23rd, 7 a.m. AEST January 24th.


Agenda / Minutes:

  • Pivotal Tracker or JIRA? (Mark: I'm fine with using either, and I'll make sure that the PUI epic stories in JIRA get wrapped up either way; if we use PT, then a few new users will need to be added; if we use JIRA, a few new stories will need to be added to better align with the remaining scope of work.)
    • We'll use JIRA.
    • We'll create new tickets for the single-scroll view (item 3) and link it to AR-838; ditto for the container / hierarchy-free view (item 10). Those item numbers reference the remaining scope of work document.
    • James will create a new JIRA filter for these tickets
  • Let HM take it from there regarding Sprint 1 (1/23 - 2/3)
    • HM will work on the single-scroll view ticket to the first sprint.
    • HM will also start working on the plugin-ification ticket, as well, for the first sprint, although this might not be done in a single sprint.
    • Need to create a new ticket for AR-1546 to better align with 6 from the scope of work document
    • Also need to create tickets for 2.b and 2.c from the scope of work document (and maybe a few others, such as 14.c depending on how that's implemented).
    • Note regarding single-scroll view:  inherited information should not display repeatedly.  NYPL design is pretty spot on for what's desired (e.g. http://archives.nypl.org/scm/20562#detailed), although 1) to fit the CH designs the sub-navigation menu would probably need to be on the right-hand side, and 2) container information needn't be out in front, especially since it's repeatable in ASpace and not as strictly locked down as in the NYPL site, which can get away with just displaying something like "b.1 f.1"
  • next meeting?
    • February 6th, 3 p.m., EST