|20||Proposal for a simple issue tracker within FOLIO|
Carsten Schwill (SUB Hamburg)
Presentation for download.
SUB HH is a small consortium,a member of GBV, operating 10 tenants in OLCL PICA LBS4.
Proposes implementing within FOLIO a lightweight ticket system for day-to-day tasks. Not to replace JIRA, need that for development, but is heavy weight. Useful to have something lightweight for communications between library staff and technical personnel. E.g.:
Project phases that could benefit:
FOLIO tickets may be used by operations team, loan service desk, complain management, bib updates, in-house IT services.
What does lightweight mean? Few data elements, manual workflow is tracked, due dates, priorities, severity.
Can the tickets persist between installations? Maybe not, but perhaps can migrate the backing store.
Question: can we integrate FOLIO with an existing, mature ticketing app rather than re-implementing? Might get quicker traction.
Motivation is to have something more lightweight to administer JIRA or RequestTracker. Not incompatible with integration with a more robust system.
|WOLFCon final agenda|
|Desired Wolfcon outcomes|
Will help us have more conference discussions
|WOLFCon logistics||have we confirmed locations for sessions?|
|15||List of Integrations|
Source System Information
Borrowed from OLE, useful to see which sites have similar integrations and can help each other.
Will move to SysOps folder, link to from wiki, and bring to PC to get help filling in.
|LS Tools at Cornell|
|topics proposed for further meetings|
|Orchestration tools||see the discussion last week|
|Closing words||we will skip next meeting and meet again 05/17 - or on WOLFCon !|