Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Instance records - part 2

Description

.Create an instance entity that supports the following:

Story part

Field name

Display field name

Data type

Operators

Values

Notes

2

statisticalCodeIds

Statistical code

Array of strings

==, !=, in, not in

Dropdown of pre-populated statistical code types combined with statistical code names based on existing statistical code ids in the format:

<statisticalCodeType.name>: <statisticalCode.code> -<statisticalCode.name>

The values should be retrieved dynamically from /statistical-codes endpoint

The values should be retrieved dynamically from /statistical-code-types and /statistical-codes endpoints

2

statusId

Status

String

==, !=, in, not in

Dropdown of pre-populated statuses names based on existing statuses ids.

The values should be retrieved dynamically from /instance-statuses endpoint

2

contributors.Type

Contributors type

Array of objects 

==, !=, in, not in

Dropdown of pre-populated contributor type names based on existing contributor types ids

The values should be retrieved dynamically from /contributor-types endpoint

2

modeOfIssuanceId

Mode of issuance

String

==, !=, in, not in

Dropdown of pre-populated modes of issuance based on mode of issuance ids

The values should be retrieved dynamically from /modes-of-issuance endpoint

Requirements:

  • The fields identified above are available in the query builder for the instance entity type

  • When a field identified above is selected in the query builder:

    • the 'operators' identified in the table above are available

    • the type of 'value' identified in the table above are available

    • pre-populated values appear in alphabetical order 

  • The fields identified above are available columns for lists of a holdings entity type

  • Field names use sentence casing (only first letter of first word is capitalized) 

  • Fields are alphabetically ordered

  • Unit and API tests are written/updated and they pass

  • The test code coverage is >80%

 

 

 

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

Activity

Show:

Emma_HaroyanMarch 15, 2024 at 12:13 PM

Hey The test cases are ready for your review.

Emma_HaroyanMarch 14, 2024 at 7:50 AM

Hey Kriti.

Everything looks good, array type fields I checked via Postman, all was okay, here is the example

But, I have to move the ticket to ‘Blocked’, because I wasn’t able to verify the field ‘Instance status’, as I see it has '"queryable": false, which is incorrect, because Instance status is a string type.

I’ve created a bug ticket for Noah, after the fix I will check the field at a part of your ticket and hopefully will close it

https://folio-org.atlassian.net/browse/MODFQMMGR-200

Kriti JainFebruary 28, 2024 at 1:12 PM
Edited

you can post the query which took time.

I suppose it would be acceptable to proceed with moving the ticket, considering that other tickets addressing similar issues are also progressing

Emma_HaroyanFebruary 28, 2024 at 9:56 AM

Tested on int env.

I checked for “Instance mode of issuance” and “Instance status”, everything worked, but there was a bit time delay, I ran a query, and I had to wait for ~10 min to see the result. Can we somehow improve it?

Also verified the rest 2 fields via postman, seems to be okay.

But I think I should move the ticket to ‘In review’ only when all of the fields are available through UI, right?

Kriti JainFebruary 27, 2024 at 8:54 PM
Edited

you will be able to test Status and Mode of Issuance through UI. The others are array type drop down which is currently not supported. They will appear as drop down when firebirds work is done

For checking statisticalcode field you can post a query like

For checking contributors field you can post a query like this

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Corsair

Fix versions

Release

Quesnelia (R1 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 19, 2024 at 3:02 PM
Updated March 19, 2024 at 1:44 PM
Resolved March 15, 2024 at 9:35 PM
TestRail: Cases
TestRail: Runs