BA's Open Issues

Owned by Kathleen Gerdink (Unlicensed)
Last updated: Jul 19, 2012

Working page to track requirements and planning issues with BA's- initial page created per Patty to document working discussion items 

Quicklinks/Table of Contents:


Action Items

Working list to be added to and used to frame some planning discussions, especially around Patty's July 11-20 visit to Bloomington. This Action Items section is part notes/part possible action items per PM/KG call 6/29/12.

  1. Tiger Teams and Meeting changes
    1. Next Action Item: TBD- PM to attend some calls; clear roles
    2. No more Monday TT or HTC calls
    3. S&A moved to Wednesday, 9am
    4. Need to address double-meetings (S&A, Editors)
    5. See new roles and responsibilities document
    6. Where are we with specs?
    7. Need to address:
      1. Tuesday, SA/BA/Core call, 8:30- next is July 18?
      2. Wednesday: Project team- 9am timeslot usurped by S&A TT standing call moved?
      3. Friday: Product Owner call, 10am-12pm
    8. PM meeting 6/27: mentioned 1-2 day meeting while in Bton on planning?
  2. Spec Progress
    1. Next Action Item: review when PM in Bton
    2. OLE Scope & Schedule folder
    3. OLE 0.8 Jira
    4. PM wants "where are we at with specs"
      1. by TT
      2. by Dan
      3. by Kathy
    5. overdue on Roadmap
    6. roadblocks
    7. how to organize, modules
    8. going forward: SA vs BA
  3. SEARCH
    1. Next Action item: distribute mini-search spec to each TT for completion
    2. Federated Search (Google Docs folder)
    3. Simplify approach
    4. KG to create Q&A, form templates for each Tiger Team to complete for functional Search needs and desired fields
      1. links to TST, DEMO and info
      2. existing functions
      3. new features
      4. in progress
    5. To compile global requirements, then possibly work with SI team
      1. then UI edits
      2. indexing and performance issues
      3. KNS vs SOLR
      4. sample records
    6. Acceptance Criteria, Test Scripts- backward, forwards
    7. Above to enable regression testing as features added
  4. INSTANCE
    1. Next Action item: possible meeting July 16 or 17 (TBD with PM)
    2. Instance 9.x (google docs folder)
    3. Get key stakeholders in a meeting, and review critical issues- make decisions (KG to summarize existing documentation, work with Patty to prep)
    4. Possible attendees: Patty, Peri, John P, Kathy, Gary C, Frances M, Michelle S, Doreen H
    5. Plan TBD with Patty Jul 9 +
  5. PURAP/KFS Prioritization
    1. Next Action Item: KG, PM to review
    2. Need answers on S&A additions to Roadmap
    3. where do we need more functional documentation on requirements?
    4. Need to discuss order of specs for functional and technical dependencies (what constitutes forking, how documenting, what waits for 5.0)
      1. SFC and fund rules
      2. Roles Workflows
      3. Order Types
      4. vs overdue specs
      5. Deposit accounts and other 0.8 PREQ features (vs post KFS 5 upgrade and PREQ M:1 edits)
    5. Peri & Patty- meeting to review app
    6. With Kathy and team: review KFS for what being used; what need to remove; overview future or in progress features 
  6. DESCRIBE- DOCSTORE
    1. Next Action item: have sit-down on Describe (date, who- TBD with PM)
    2. what features coded: docstore, bib, instance, search
    3. what coming
    4. how to prioritize Doc controls policies and: doc ownership, doc status, audit trail; work units, item availability, transaction links
    5. try to simplify fundamental issues with team and BA
    6. coordinating and communicating Editors work; BA vs SA
  7. DELIVER
    1. Next action item: TBD
    2. what issues outstanding?
    3. Key infrastructure in progress (baseline needed for all specs): Patron, Policy, Item, Item Status, Location
    4. TBD: Circ Desk (dependency with work unit, doc ownership, KIM and Locations extension)
    5. Next Patron enhancements and defining needs for 1.0
    6. GoKB competing- Dan going 50%
    7. Dan- other critical issues?

Additional discussions required

The following is based on items not yet discussed, but listed in several outstanding or planning lists, esp around roadblocks or decisions for OLE 0.8 or 1.0 coding and spec-writing.

Future: By Functional Module or Specific Requirements/Features

(This section is placeholder, as possible template going forward to track open issues by functional module- to begin to list functional or infrastructure issues - will need to improve outline or approach, maybe child or functional wiki pages - TBD with PM)

Acquisitions
  • Tiger Team: Select & Acquire (SA: Bob Persing)
  • Library Functions: Select, Acquire
  • Rice 1/KFS: PURAP, VENDOR, GL; KEW; KIM
  • Rice 2: Ingest/Load/Overlay records- KRAD, KRMS (SA: Michelle Suranofsky)
  • Infrastructure/dependencies/outstanding decisions:
  • Other issues/notes:
Financial, COA
  • Tiger Team: Select & Acquire (SA: Bob Persing)
  • Library Function: Acquire, Manage funds, budgeting
  • Rice 1/KFS: PURAP, COA, FS, PDP, GL, BA; KEW; KIM
  • Rice 2: N/A
  • Infrastructure/dependencies/outstanding decisions:
    • KFS 5 changes
    • Financial integrations with university systems- OLE 1.0
    • FYRO- OLE 1.5
  • Other issues/notes:
Licensing
  • Tiger Team: MER (SA: Emily Lynema)
  • Library Functions: MER, ERMS, Electronic Resources Management, Licensing
  • Rice 1/KFS: N/A
  • Rice 2: License Requests & UIs; KRAD, KRMS, KIM
  • Docstore: Agreements, Agreement Docs, (Future: Deal, Package, Agent)
  • Infrastructure/dependencies/outstanding decisions:
    • GoKB- OLE 1.0 & 1.5
  • Other issues/notes:
Cataloging
  • Tiger Team: Describe/Manage (SA: Michelle Suranofsky)
  • Library Functions: Describe, Manage, Editors, Cataloging, Technical Services
  • Rice 1/KFS: combined search
  • Rice 2: Maintenance Docs (Bib, Instance); Editors, Ingest/Load/Overlay records- KRAD, KRMS; KIM
  • Docstore: Bibliographic, Instance, (Future: Authority)
  • Infrastructure/dependencies/outstanding decisions:
    • Authority Records - OLE 1.5
    • Scoping for 1.0
  • Other issues/notes:
Editors 
  • Tiger Team: Editors (SA & Team lead: Michelle Suranofsky)
  • Library Functions: Framework for (above) cataloging
  • Rice 1/KFS: N/A
  • Rice 2: KRAD UI; Maintenance Docs (Bib, Instance)
  • Docstore: Bib, Instance, (Agreement/License thru MER)
  • Infrastructure/dependencies/outstanding decisions:
    • Framework vs individual UI's
    • Scope of system config in OLE 1.0
  • Other issues/notes:
Circulation
  • Tiger Team: Deliver (SA: Stuart Miller/Chris Case)
  • Library Functions: Circulation, Patrons
  • Rice 1/KFS: N/A
  • Rice 2: Patron, Checkout/Loans, Checkin, Policies, Maintenance Docs, etc
  • Docstore: Bib & Instance, but primary actions on Items and Locations within Instance
  • Infrastructure/dependencies/outstanding decisions:
    • Patron- further scoping, coding for 1.0
  • Other issues/notes:
Infrastructure
  • see each team and global issues
  • may belong with Technical below
  • Rice 1 vs Rice 2, and providing for future integrations
  • Docstore:  Document controls, ie Records Management; Checkin and Checkout; Search
  • Infrastructure/dependencies/outstanding decisions:
    • OLE Identity Management
      • APIs: Grouper, Shibboleth, LDAP, etc
      • KIM 1 vs 2
      • Authz/Authx
      • User loads 
      • Any original IdM, MUR- Manage User Relationships work
    • others?
  • Other issues/notes:
Technical/Systems Integration
  • Tiger Team: Systems Integration (Lead: Chris Case), Technical Council 
  • Library System Functions: Data migrations, Discovery layer, z39.50, NCIP, external interfaces; KFS & Rice upgrades; OLE Integrations/External Systems list
  • OLE: API's
  • Infrastructure/dependencies/outstanding decisions:
    • performance improvements
  • Other issues/notes:

Operated as a Community Resource by the Open Library Foundation