VCards in entry forms, list views, search indexing and visualization

[litvinovg]

VIVO GitHub issue

Vitro PR

What does this pull request do?

Added option to store participants as VCards for authorships, editorships and project participants.
Added option in editorship entry form to select organization as editor.
Added search indexing extension to index VCard participants.
Support visualization of VCard co-authors

What's new?

Modified entry forms:

• AddAuthorsToInformationResourceGenerator.java
  addAuthorsToInformationResource.ftl
  addAuthorsToInformationResource.js

• AddEditorsToInformationResourceGenerator.java
  addEditorsToInformationResource.ftl
  addEditorsToInformationResource.js

• ProjectHasParticipantGenerator.java
  projectHasParticipant.ftl

Created list view for presentation participant listViewConfig-relatedExternalSpeakerRole.xml
Applied list view for participant faux property PropertyConfig.n3

Modified editorship list view to support VCards listViewConfig-informationResourceInEditorship.xml and propStatement-informationResourceInEditorship.ftl

VCard visualization modifications:
Collaborator.java
CollaborationDataViewHelper.java
coAuthorPersonLevelD3.ftl
collaboratorToActivityCountTable.ftl

Added new properties configured in runtime.properties:
Maximum number of co-authors displayed on co-authors network.
visualization.coAuthorNetwork.maxCollaborators = 35
Prioritize co-authors stored as Persons in lists with VCard co-authors
visualization.coAuthorNetwork.personBoost = 0

How should this be tested?

This is deployed on https://vivo.tib.eu/vivorc
A description of what steps someone could take to:

• Try adding/removing participants to a publication by using authors, editors faux property:
• Add VCard participant
• Add person
• Select person from existing
• Add organization
• Select organization from existing
• For each case verify that added participant is listed in related list view
• Try adding participants to a project and presentations: vcard and real
• In person co-author network verify that vcard co-authors are visible if "Include external co-authors" is checked
• Search for VCard participants

Interested parties

@VIVO-project/vivo-committers

Reviewers' expertise

Candidates for reviewing this PR should have some of the following expertises:

1. Java
2. HTML, CSS, JavaScript
3. FreeMarker
4. SPARQL
5. Natural language knowledge
   1. English
   2. German
   3. Spanish
   4. French
   5. Portuguese
   6. Russian
   7. Serbian

Reviewers' report template

General comment

A reviewer should provide here comments and suggestions for requested changes if any.

Testing

A reviewer should briefly describe here how it was tested

Code reviewing

A reviewer should briefly describe here which part was code reviewed

[tawahle]

In my opinion, an explanation for Vcard is required. Maybe something like this: "Please select VCARD only, when the person has not and is not supposed to have a profile in VIVO. Otherwise choose the type "Person"."

[litvinovg]

In my opinion, an explanation for Vcard is required. Maybe something like this: "Please select VCARD only, when the person has not and is not supposed to have a profile in VIVO. Otherwise choose the type "Person"."

@tawahle
I modified description text as you suggested. Also fixed presentation participant form and list view.
Changes were redeployed on https://vivo.tib.eu/vivorc
Please test it once again when you have time.

[tawahle]

Everything is working fine.

[chenejac]

@litvinovg thanks for the PR. Looks nice and works well. I have posted a couple of comments.

I am wondering whether we should add a middle class between VIVOBaseGenerator on side, and AddEditorsToInformationResourceGenerator and AddAuthorsToInformationResourceGenerator on the other side, to encapsulate shared code in that middle class (for instance it might be entitled AddContributorToInformationResourceGenerator).

[chenejac]

Maybe we can use here:

Please select external co-author, when the person doesn't have and is not supposed to have a profile in VIVO. Otherwise choose the type "Person"."

[litvinovg]

Maybe. In that case VCARD option should be changed accordingly on entry form pages. In any case I think we should change all the translations altogether when there is an agreement on how it should look like to avoid changing the same thing multiple times. It was already changed once in accordance with this comment #4015 (review)