Open mconlon17 opened 7 years ago
Is the problem with vivo:middleName or with vcard:additionalName or both?
It's vivo:middleName. The use case is for editing vcard name's via the VIVO GUI that aren't attached to a foaf:Person. Though ontology-related, the change may need to be within VIVO... the domain of vcard:givenName and vcard:familyName are defined in VIVO/home/src/main/resources/rdf/tbox/filegraph/data-properties.owl.
I'm attaching two screenshots of vcard:Name objects. One already has a middle name and the field is shown, the other does not and the middle name field is missing.
Low Impact.
Existing data, and queries are unaffected. Additional investigation is needed regarding the impact on the software. Currently expected to be minor.
Opened by @gneissone
vcard:givenName and vcard:familyName both have a domain of vcard:Name. vivo:middleName does not. This makes it impossible to add a middle name to a vcard:Name in the VIVO web interface unless you specify the domain manually (or edit the name via a foaf:person editing page). Should the following domain and range be added to vivo:middleName in the ontology?
See https://jira.duraspace.org/browse/VIVO-1362