Deck
idKuali OLE
Card
labelOverview
Section
 
Column
width50%
 

Description

Batch operations are defined and the architecture is laid out in this section. Defining a batch operation begins with the definition of the batch profile and involves definition of various sections that cover different aspects of the batch job. Apart for defining the batch profile, the user may also define specific KRMS profile xml files, various maintenance documents for data mapping and define CRON schedules.

 

The execution of the batch job varies based on options selected in the profile. Current implementation of batch jobs covers ingest of bib, order, invoice, location and patron data as well as bib overlay and export of data including bibs, order and invoices. Other data operations such as deletions, 'Globally Protected Field' definition and overlays may also be covered in this definition.

Card
labelDesign: Business

User Stories

Priority Rank Order

 

Card
labelDesign: Technical

 

Design Technical
Service Design and Implementation
Screen Flow Diagram

Layout use cases based on the screen flows indicating navigation between different screens and pop-ups. 

Security
  • Roles – list of roles to be defined
  • Permissions – list of permissions to be defined
  • User Profiles – user profiles that may be applied roles/permissions (also for test/mock purposes) 
Rules
  • Context & Agendas
  • Terms & Prepositions
  • Sample XML file
Component Design
  • OJB.xml
  • Class Diagram

Image Added

 

  • State Chart Diagram
Service Contracts
Service Implementation
Card
labelUI Screen

 UI Screen

 

Card
labelData Model

Data Model

Entity : BATCH DEFINITION

 

Name

Max
Len

Data Type

Default Value

Input Type

Action Event

Action Event Function Name

Validation
Type

Tab Index

Remarks