Page Comparison

...

Non-functional Requirements

1. Interoperabilty - The solution should allow seamless integration with Card Printing Hardware/Software

2. Auditability - The solution should provide capability of tracking what patron data was exported for printing by whom and when.

Assumptions

1. LoC uses Windows-based workstations at registration desks

2. LoC uses ZC100 Card Printer for printing cards and its native software (Zebra CardStudio)

3. The target solution may be implemented with the intermediate manual flow-based solution

Target Architecture

Context Diagram

FOLIO is a web based application and the UI is provided through web browser. This is limiting capability of interaction with hardware. The solution addressse interoperability NFR through implementation of desktop application that would provide middleware capability for synchronization of data between FOLIO and printing hardware.

...

1. API to export data for printing in Excel format and related profile pictures

2. API to update patron’s record with print date and related details

3. Capability to track what patron data was exported for printing by whom and when.

Middleware should provide:

...

1. Middleware is desktop application (windows service) that is aimed to synchronize local data for printing patron cards with FOLIO

2. User should be logged in his LC desktop and authorize Middleware to fetch the data from FOLIO

3. The export of newly created records should happen in background without interaction

4. User should be able to manually invoke synchronization with FOLIO

...

Sequence Diagram

...