MARCcat: MARC Bibliographic records (UXPROD-786)

[UXPROD-1460] Management of Name-Title heading in MARCcat Bibs Created: 24/Jan/19  Updated: 19/Jan/21  Resolved: 03/Apr/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: MARCcat: MARC Bibliographic records

Type: New Feature Priority: P3
Reporter: Annalisa Di Sabato Assignee: Tiziana Possemato
Resolution: Done Votes: 0
Labels: Heading, MARCcat-Bib, Name-Title, cap-mvp, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft PowerPoint NAME_TITLE management_David_prototype.pptx    
Issue links:
Defines
defines UXPROD-786 MARCcat: MARC Bibliographic records Closed
Relates
relates to UXPROD-922 Heading - Management (cross-reference... Closed
relates to UXPROD-2496 Management of Name-Title heading in M... Closed
Requires
requires MODCAT-110 Creation of Name-Title heading behind... Closed
Epic Link: MARCcat: MARC Bibliographic records
Analysis Estimate: Large < 10 days
Front End Estimate: Large < 10 days
Front End Estimator: Matteo Pascucci
Back End Estimate: Large < 10 days
Back End Estimator: carmentrazza
Development Team: @cult
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R5
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Management of name-title heading in MARCcat based on David's prototype.
In this prototype Davis suggested tuo options to display and manage NT.
From meeting notes (https://folio-org.atlassian.net/wiki/display/MM/2018-12-03+MARCcat+Subgroup+Meeting+Notes):
"Group liked the simplicity of Option B, but the options of browsing that Option A allows. The ability to get to Option B from Option A using the top menu (Where it says, "Access point") was seen as a way that both options could be used. There are concerns about the size of the font and ability to read in Option A since there is so much information squeezed into one screen."



 Comments   
Comment by carmentrazza [ 01/Apr/20 ]

The required changes have been made both on the back-end and on the front-end.
Back-end :

  • creation of Name/Title headings
  • creation of Names/Title tags

Front-end:

  • enabling indexes Name/Title for Name and Name/Title for Title only for Browse
  • enable BIB1 column with NTK index for records.

The Name / Title feature involves creating name / title tags and the browse search records.

Comment by carmentrazza [ 01/Apr/20 ]

The creation of the name / title tags fails for this reason:

Batch entry 0 insert into amicus.NME_ACS_PNT (NME_WRK_RLTR_CDE, MTRL_SPCFY_TXT, INTTN_WHICH_FLD_APLY_CDE, NME_WRK_RLTR_STRNG_TXT, NME_OTHER_SBFLDS, NME_SEQ_NBR, NME_HDG_NBR, BIB_ITM_NBR, NME_TTL_HDG_NBR, USR_VW_IND, NME_FNCTN_CDE) values (NULL, NULL, NULL, NULL, NULL, NULL, 110, 213, 2, '1000000000000000', 0) was aborted: ERROR: insert or update on table "nme_acs_pnt" violates foreign key constraint "nme_acs_pnt_fk3"
Detail: Key (nme_fnctn_cde)=(0) is not present in table "t_nme_fnctn". Call getNextException to see other errors in the batch.

This NME_FNCTN_CDE column must have for tag Name/ Title must be equal to 0.

You have to assign the bug to Mirko

Comment by Mirko Fonzo [ 01/Apr/20 ]

The following list shows the allowed values for the column NME_ACS_PNT.nme_fnctn_cde, the value 0 is not present:

1 => "Added Entry - Not specified"
2 => "Main Entry - Undefined"
3 => "Main Entry-Main entry/subject relationship irrelevant (OBSOLETE)"
4 => "Main Entry - Main entry is subject of the work (OBSOLETE)"
7 => "Added Entry - Information not provided"
8 => "Added Entry - Analytical entry"
9 => "Added Entry - Alternative entry (OBSOLETE)"
10 => "Added Entry - Secondary entry (OBSOLETE)"
11 => "Added Entry - Supplementary secondary entry (OBSOLETE)"
16 => "Main Entry - Not specified"

What the value 0 is intended for?
If a suitable alternative value is not in the list, we have to add a proper one.

Comment by carmentrazza [ 01/Apr/20 ]

For the creation of the title name tags we need to insert the code 0.
I had verified that the table does not provide it.
This is how it works in Olisuite too.
A solution must be found to the problem.

Comment by Mirko Fonzo [ 01/Apr/20 ]

A proper new entry point has been added to the tables T_TTL_FNCTN and T_NME_FNCTN.
This Issue will be added to the MARCcat Database patch 1.4.
Please attempt again the test in our test environment where the SQL updates have been installed.

Comment by carmentrazza [ 01/Apr/20 ]

Now, I have another error:

Batch entry 0 insert into amicus.TTL_ACS_PNT (TTL_SRS_ISSN_NBR, TTL_SCDRY_FNCTN_CDE, INTTN_WHICH_FLD_APLY_CDE, TTL_VOL_NBR_DSC, MTRL_SPCFY_TXT, VRNT_TTL_DSPLY_CDE_TXT, SEQ_NBR, TTL_HDG_NBR, BIB_ITM_NBR, NME_TTL_HDG_NBR, USR_VW_IND, TTL_FNCTN_CDE) values (NULL, 0, NULL, NULL, NULL, NULL, NULL, 129, 220, 3, '1000000000000000', 0) was aborted: ERROR: insert or update on table "ttl_acs_pnt" violates foreign key constraint "ttl_acs_pnt_fk4"
Detail: Key (ttl_scdry_fnctn_cde)=(0) is not present in table "t_ttl_scdry_fnctn".

For Title/Name tags TTL_ACS_PNT the columns have a value of 0:

  • TTL_FNCTN_CDE
  • TTL_SCDRY_FNCTN_CDE
    Check T_ connected for this columns .
Comment by Mirko Fonzo [ 01/Apr/20 ]

I've added the required records to the T_TTL_SCDRY_FNCTN table.
Please make another test.

Comment by Mirko Fonzo [ 03/Apr/20 ]

One more issue has been found.
It prevents the trigger "ttl_acs_pnt_i" to operate by inserting a new record into ttl_acs_pnt_plus_refs tables.
Here an example of the error which could be traced into the log:

insert into amicus.TTL_ACS_PNT (TTL_SRS_ISSN_NBR, TTL_SCDRY_FNCTN_CDE, INTTN_WHICH_FLD_APLY_CDE, TTL_VOL_NBR_DSC, MTRL_SPCFY_TXT, VRNT_TTL_DSPLY_CDE_TXT, SEQ_NBR, TTL_HDG_NBR, BIB_ITM_NBR, NME_TTL_HDG_NBR, USR_VW_IND, TTL_FNCTN_CDE)
values (NULL, 0, NULL, NULL, NULL, NULL, NULL, 146, 266, 6, '1000000000000000', 0);
was aborted: ERROR: duplicate key value violates unique constraint "ttl_acs_pnt_plus_refs_pk"
Detail: Key (ttl_hdg_nbr, bib_itm_nbr, usr_vw_ind)=(146, 266, 1000000000000000) already exists.

The issue has been fixed with the MARCCat DB 1.4 patch.

Comment by Annalisa Di Sabato [ 03/Apr/20 ]

The test was successfull

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