chenejac / VIVOTestMigrationJIRA

0 stars 0 forks source link

VIVO-1829: In "Other" tab of People section, several items display as URI #1720

Closed chenejac closed 3 years ago

chenejac commented 4 years ago

Nicolas B Dickn (Migrated from VIVO-1829) said:

In the tab

People > [some individual] > Other

and in the following sub-tabs :

Some (but not all) items displays as URI, regardless of the language selected.

The base dataset used is : [https://github.com/UQAM-VIVO/VTE-config/blob/master/Data/ExempleGraphe/sample-data-fr_localhost-vivo.ttl] and data was added to several fields during the testing process.  

chenejac commented 4 years ago

Andrew Woods said:

This seems like a data issue. If the resource (e.g. http://localhost:8080/vivo/individual/n1697) had an rdf:label, the label would be displayed. I would suggest moving this ticket out of the sprint.

chenejac commented 3 years ago

Benjamin Gross said:

I cannot reproduce this issue. [~accountid:60785ded115da6006f540529] suspected it may have been a data issue. 

The 'bearer of' and 'has contact info' object properties are only visible to the root user. There are 'faux property' relationships and forms that should correctly define the context nodes that use 'bearer of' and 'has contact info.' [~accountid:70121:d6633ae6-182e-4293-a5d8-41f16a4519d5], can you describe how the data was added that resulted in this issue? 

chenejac commented 3 years ago

Nicolas B Dickn said:

The data integration in our developement environment has been done by [~accountid:5d7a3f78458a170db4b08b25]. I'll ask him.

chenejac commented 3 years ago

Nicolas B Dickn said:

Ok, obviously a data related bug. In my current insall, the 'has contact info' still show up as an URI, but it makes sense as the vcard shouldn't have an rdf:label. As for the 'bearer of', I tried adding data manually, and it shows up correctly.

I think we can not only remove the ticket from the sprint, but close it altogether.

chenejac commented 3 years ago

Benjamin Gross said:

Thanks [~accountid:70121:d6633ae6-182e-4293-a5d8-41f16a4519d5], if the problem crops up again we can revisit.