Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODSOURCE-352 |
---|
|
...
Here is a list of steps, each step covers some area in a corresponding module. I added raw estimations to the steps that Spitfire can implement, other steps require the help of the Falcon team in estimating.
- Create default Action profile and Mapping profile schema for Authority domain object
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDICOREMODINV-180 |
---|
|
Create processor to generate Authority domain objects from Marc records by the mapping rules - Create default Action profile and Mapping profile
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDICORE-181180 |
---|
|
- Create mapping rules
Jira Legacy |
---|
server | System JiraJIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODSOURMAN-573 |
---|
|
- Create schema for processor to generate Authority domain object objects from Marc records by the mapping rules
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVMODDICORE-504181 |
---|
|
- Create Handler CRUD REST API to generate receive Authority domain objects from Marc records object and save it into storage
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVMODINVSTOR-501 |
---|
|
Handle an update of Authority record via mod-quick-marc - Create Handler to generate Authority domain objects from Marc records
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINV-503 |
---|
|
Create CRUD REST API to receive Authority domain object and save it into storage - Handle an update of Authority record via mod-quick-marc
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVSTORMODINV-787503 |
---|
|
- Automatic creation of "authority" Kafka topic
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVSTOR-788 |
---|
|
- Sending of "Domain Events" to Kafka topic when Authority record is created/updated/deleted
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVSTOR-789 |
---|
|
Spike to created additional stories for the mod-search - Add search API for Authority Records
Jira Legacy |
---|
server | System JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MSEARCH-195 |
---|
|
- Add /authorities/ids API for Authority Records search
Jira Legacy |
---|
server | System JiraJIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MSEARCH-187 |
---|
|
Approximate steps:
- Create a new subscriber for Kafka topic to receive Authority domain events (mod-search)
- Create index mapping to use appropriate ElasticSearch field types for authority fields (mod-search)
- Provide REST API to retrieve Authority Ids stream (mod-search) - Performance testing - story points to be defined
- Karate tests ???
- Refactor /index API to support Authority Records
Jira Legacy |
---|
server | System JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MSEARCH-196 |
---|
|
- Create Karate tests to cover Authority Records search in mod-search
Jira Legacy |
---|
server | System JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | FAT-990 |
---|
|
- Mod-search Authority Records search performance tests
Jira Legacy |
---|
server | System JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | PERF-200 |
---|
|
Separate searching for heading values (1xx) and auxiliary values (4xx 5xx)
...