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

[UXPROD-2681] Folijet support work for Single record OCLC import Created: 23/Sep/20  Updated: 28/Apr/21  Resolved: 09/Feb/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 1
Labels: data-import, epam-folijet
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODDATAIMP-370 OCLC single record import: Updates do... Closed
is defined by MODDATAIMP-381 Inventory Single record import Update... Closed
is defined by MODDICONV-158 Update the names and descriptions of ... Closed
is defined by MODDICONV-160 Update the names and descriptions of ... Closed
is defined by MODDICONV-176 Update the names and descriptions of ... Closed
is defined by MODSOURMAN-372 Describe a documentation for OCLC imp... Closed
is defined by MODSOURMAN-385 Enable OCLC update processing Closed
is defined by MODSOURMAN-419 SQL Exception WRT count function Closed
is defined by MODSOURMAN-434 marc rejected.. for unknown reasons -... Closed
is defined by UIDATIMP-784 Disallow UI edit & deletion of the Sy... Closed
is defined by UIDATIMP-819 Suppress OCLC Single record import jo... Closed
is defined by UIDATIMP-833 Suppress OCLC Single record import ma... Closed
is defined by UIDATIMP-834 Suppress OCLC Single record import ac... Closed
is defined by MODDICONV-148 Create default OCLC Create Instance p... Closed
is defined by MODDICONV-149 Create default OCLC Update Instance p... Closed
is defined by MODSOURMAN-407 Create JobExecution seems to require ... Closed
is defined by UIDATIMP-659 Suppress Inventory single record MARC... Closed
is defined by UIDATIMP-671 Add filter for Inventory single recor... Closed
is defined by MODSOURMAN-405 Require pubsub.events.post Closed
is defined by MODSOURMAN-433 If user has no "personal" property, d... Closed
Requires
is required by UXPROD-976 Import individual MARC record from OC... Closed
is required by UXPROD-2804 Import individual MARC record from OC... Closed
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Medium < 5 days
Front End Estimator: Oleksii Kuzminov
Back End Estimate: Large < 10 days
Back End Estimator: Oleksii Kuzminov
Development Team: Folijet
PO Rank: 98
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R1
Rank: MI State-Lib of MI (Sum 2021): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Folijet will likely need to do some support work in Data Import for the Index Data development of single record import from OCLC.

Per Oleksii - better to have a separate profile for Create (not use the secret button profile), so that it's easier to identify what triggered the profile

Technical overview of Folijet design for this: https://docs.google.com/document/d/1T0DINfjnXIgB5dZGiQbi77jIAXCdLkULyx_hTELwvdY/edit?usp=sharing



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 14/Oct/20 ]

Hi Mike Gorrell I finalized the Folijet support stories for Single record OCLC import, and will be grooming them with Folijet. They are all linked to this feature. Please review them and let me know if any questions or comments

Comment by Volodymyr Rohach [ 02/Dec/20 ]

Hello everyone!
Default OCLC profiles for Create and Update Instance were added.You can see them on the envs.

OCLC Job Profile for create Instance:
id: "d0ebb7b0-2f0f-11eb-adc1-0242ac120002"
name: "OCLC Create Instance"
More information about this job profile you can check here: https://folio-org.atlassian.net/browse/MODDICONV-148

OCLC Job Profile for update Instance:
id: "91f9b8d6-d80e-4727-9783-73fb53e3c786"
name: "Default OCLC update Instance"
More information about this job profile you can check here: https://folio-org.atlassian.net/browse/MODDICONV-149

Thank you!
CC: Ann-Marie Breaux Oleksii Kuzminov

Comment by Volodymyr Rohach [ 07/Dec/20 ]

Hello everyone!
There are some examples for the filtering queries by specific jobProfiles:

1. /metadata-provider/jobExecutions?limit=100&query=jobProfileInfo="\“id\“==d0ebb7b0-2f0f-11eb-adc1-0242ac120002"
The result will be - all jobExecutions with specific jobProfileInfo Id. (In this case: "d0ebb7b0-2f0f-11eb-adc1-0242ac120002" - "OCLC Create Instance")

2. /metadata-provider/jobExecutions?limit=100&query=(jobProfileInfo="\“id\“==" NOT jobProfileInfo="\“id\“=="d0ebb7b0-2f0f-11eb-adc1-0242ac120002")
The result will be - all jobExecutions without specific jobProfileInfo Id. (In this case: "d0ebb7b0-2f0f-11eb-adc1-0242ac120002" - "OCLC Create Instance")

3./metadata-provider/jobExecutions?limit=100&query=(jobProfileInfo="\“id\“==d0ebb7b0-2f0f-11eb-adc1-0242ac120002") OR (jobProfileInfo="\“id\“==91f9b8d6-d80e-4727-9783-73fb53e3c786")
The result will be - all jobExecutions with 2 Default jobProfiles.With first or second one. (In this case: "d0ebb7b0-2f0f-11eb-adc1-0242ac120002" - "OCLC Create Instance", "91f9b8d6-d80e-4727-9783-73fb53e3c786"- "Default OCLC update Instance")

CC: Ivan Kryzhanovskyi Mariia Aloshyna Oleksii Kuzminov

Comment by Ann-Marie Breaux (Inactive) [ 07/Dec/20 ]

Thanks very much for adding these details, Volodymyr Rohach!

Comment by Volodymyr Rohach [ 11/Dec/20 ]

Hello everyone!
Names for the OCLC default job profiles were updated (Ids still the same).
So, now:

OCLC Job Profile for create Instance:
"OCLC - Default Create Instance"

OCLC Job Profile for update Instance:
"OCLC - Default Update Instance"

CC: Ann-Marie Breaux Oleksii Kuzminov

Comment by Volodymyr Rohach [ 17/Dec/20 ]

Hello Ann-Marie Breaux!

It seems like we found one issue for logs with Mariia Aloshyna.
In https://folio-org.atlassian.net/browse/UIDATIMP-187 there is a requirement, that user should click on "file name hotlink on a row in the Landing page log" for showing
result JSON-log.

In this case, when we use data-import via CLI (for example, the case when other guys will use our data-import
via Default OCLC profiles, through HTTP-requests), we can`t set specific "filename".

And there will be one problem: if the filename is empty, then we can`t "click" on this one(It can be done, but there is just a small point that is really hard to catch and click on it).

So, Ann-Marie Breaux, what do you think: should we set a specific default filename when it is empty(from Back-end side), or should UI change this? For example, not just clicking on "filename".
Or do you have any other suggestions regarding it?

Thank you!

CC:Oleksii Kuzminov Mariia Aloshyna

Generated at Fri Feb 09 00:25:58 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.