Hello !

It seems like we found one issue for logs with .
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, , 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:

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:

Thanks very much for adding these details, !

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:

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: