Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Create default Action profile and Mapping profile (data-import-processing-core) - 2 story points
  • (+-) Create processor to generate Authority domain objects from Marc records by the mapping rules (data-import-processing-core) - 2 story points
  • Create mapping rules (mod-source-record-manager) - 2 story points
  • Create schema for Authority domain object (mod-inventory) - 2 story points
  • Create Handler to generate Authority domain objects from Marc records (mod-inventory) - 3 story points
  • Create CRUD REST API to receive Authority domain object and save it into storage (mod-inventory-storage) - story points to be definedsending it to mod-search after 
  • Automatic creation of "authority" Kafka topic (mod-inventory-storage) - story points to be defined
  • Sending of "Domain Events" to Kafka topic when Authority record is created/updated/deleted (mod-inventory-storage) - story points to be defined
  • Create new subscriber for Kafka topic , to receive Authority domain object, map it to ElasticSearch document, store in ElasticSearch events (mod-search) - story points to be defined
  • Create index mapping to use appropriate ElasticSearch field types for authority fields (mod-search) - story points to be defined
  • Provide REST API to retrieve Authority Ids stream (mod-search) - story points to be defined
  • Performance testing - story points to be defined

Separate searching for heading values (1xx) and auxiliary values (4xx 5xx)

In order to support separate search in heading values (1xx) only and over heading values (1xx) and auxiliary values (4xx 5xx) the 2 separate fields should be created in Inventory (and Elasticsearch) for each field, that user should be able to search in.