Jira Ticket
1. Summary
When a library requests material from a vendor, OLE expects the the pricing information along with the bibliographic data to be sent in paired files. The first file is of type .mrc that contains bibliographic information and a second file is of type .edi that contains the transactional information such as price, quantity etc. OLE then takes the paired files and persists the bib information in docstore along with the transactional information in the form of an OLE Requisition(s) and an OLE Purchase Order(s) through a process called Ingest. During ingest there are rules and workflows that may need to be applied and could differ for libraries depending on the various vendors and hence the concept of a "Profile" was introduced.
Profile(s) is a simple set of rules and actions along with default values that are needed for a successful ingest. The current implementation of a building an OLE Profile uses the Kuali Rules Management System (KRMS) where the different rules and actions are stored in the rules repository.
Ingest Spec
2. Data Model
KRMS Data Model
OLE_PROFILE_FACT_T - For a given term (e.x. ISBN) within an agenda (i.e. profile name such as YBP), the match points for incoming field and existing fields (i.e. 020a from incoming marc file to be matched with 020a in solr). Similarly there can be other entries such as Author and match on incoming 100a with 100a in existing solr.
OLE_PROFILE_ATTR_T - This table has default values for a given agenda.
3. Execution Workflow
a. Profile Creation
b. Ingest
