Batch Importer (Bib/Acq) (UXPROD-47)

[MODDATAIMP-2] Batch Loader: Create Folio app skeleton Created: 14/Sep/18  Updated: 13/May/19  Resolved: 20/Mar/19

Status: Closed
Project: mod-data-import
Components: None
Affects versions: None
Fix versions: 1.0.0
Parent: Batch Importer (Bib/Acq)

Type: Umbrella Priority: P3
Reporter: Oleksii Popov Assignee: Unassigned
Resolution: Done Votes: 0
Labels: data-import, epam-folijet
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODDATAIMP-14 Create mod-data-import module Closed
relates to MODSOURCE-1 Create mod-source-record-storage module Closed
relates to UIDATIMP-1 Batch Loader: Create Stripes app Closed
relates to MODDATAIMP-1 Initial design for Batch Loader flow Closed
relates to MODSOURMAN-1 Create Source records Manager module Closed
relates to UXPROD-656 Data Import (Batch Importer for Bib A... Closed
Sprint:
Development Team: Folijet
Epic Link: Batch Importer (Bib/Acq)

 Description   

Create a basic skeleton for future server-side batch loader application:

  1. create repository
  2. create a base skeleton for an application
  3. configure raml + metadata module
  4. configure module descriptor
  5. configure deployment descriptor
  6. configure jenkins file
  7. implement DB connector
  8. create 2nd module - MARC storage
  9. design data structure for metadata


 Comments   
Comment by Marc Johnson [ 14/Sep/18 ]

My understanding is that each module should have it's own JIRA project.

This looks like the beginning of a new module (Similarly UIDATIMP-1 Closed ), so this probably belongs in it's own project. Jakub Skoczen Cate Boerema John Malconian what do you think?

Comment by John Malconian [ 14/Sep/18 ]

Yep. Each module should have it's own Jira project so that we can track releases effectively. I can create the Jira project. Just need a module name.

Comment by Ann-Marie Breaux (Inactive) [ 07/Feb/19 ]

Taras Spashchenko Oleksii Popov OK to close this umbrella issue?

Generated at Thu Feb 08 23:13:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.