lsteele
February 9, 2022, 2:35pm
#1
Hi,
Hi @lsteele ,
Not a workaround, and not exactly the same as you are noting, there is a desire to be able to address this as noted in this issue:
opened 12:39PM - 15 Apr 20 UTC
OJS/OMP/OPS should present different contributor roles more clearly. At the mome… nt there is a theoretical ability to create different kinds of contributor roles, but in reality they are all treated as "authors".
When you add for example a translator and photographer contributors to an article, these contributors are shown the same way as the author in OJS templates and in the metadata exports.
### Current approach to distinguish roles:
UserGroups have a `showTitle` attribute. When it is selected, the name of the role should be visible behind the contributors name. This is used in the `getAuthorString` function. https://github.com/pkp/pkp-lib/blob/master/classes/publication/PKPPublication.inc.php#L130
### Shortcomings of the current approach:
Almost the only place where `getAuthorString` is used is the TOC. This means that for example in the Landing Page and the Crossref Metadata exports **all contributors are presented as regular authors**. This is especially bad when data is exported.
With citation formats the Translator always has a fixed position in the citation and Google Scholar specifically mentions that _only_ actual authors should be listed in the tags https://scholar.google.com/intl/en/scholar/inclusion.html#indexing which is not happening now.
### New approach:
This is open to discussion, but IMO we need a UserGroup setting for defining which of the existing userGroups are actual **Author** roles (usually just one) and which are auxiliary roles. And for some Auxiliary roles, like **Translator**, we need to have specific ways of handling the contributors assigned to that role/userGroup ie. showing/listing them in the correct place and with the correct metadata attributes.
**So in short, we need the ability to apply a taxonomy to the UserGroups and we need to code some functionalities to some of the roles listed in the taxonomy.**
The setting could be for example a pull down / radio group with labels like "Treat the Contributors in this group as Authors", "Treat the Contributors in this group as Translators" etc.
For visual presentation in the TOC and Landing page, the showTitle attribute is probably a good approach, but it needs to be taken into account also in getFullName https://github.com/pkp/pkp-lib/blob/master/classes/submission/PKPAuthor.inc.php#L65.
### Places where the contributor role needs to be considered:
- If enabled in userGroup settings, show the contributor name and the contributor role in parenthesis: TOC, Landing page, Contributors grid
- Follow the citation standard: citationStyleLanguage plugin
- Follow the used metadata schema: OAI-PMH, DOAJ export, Crossref export, ORCID, Google Scholar, DC, etc.
### Taxonomy:
Using the CASRAI CRediT standard is suggested here: https://github.com/pkp/pkp-lib/issues/857
However, I do not see how it would help a lot with this problem. The important thing here is that we need to tie different actions to specific contributor roles. For this we need a more simple taxonomy with the most usual roles.
Different citation standards usually distinquish at least between the author, editor and translator.
DC has a huge list of possible roles: http://memory.loc.gov/diglib/loc.terms/relators/dc-contributor.html
Crossref has these contributor_role values: author, editor, chair, reviewer, review-assistant, stats-reviewer, reviewer-external, reader, translator
ORCID has these contributor_role values: author, assignee, editor, chair-or-translator, co-investigator, co-inventor, graduate-student, other-inventor, principal-investigator, postdoctoral-researcher, support-staff
**IMO we could go far just by having the ability to define between three types of Contributors: authors, translators, other.**
- Contibutors belonging to a userGroup marked as "Author" would be listed as authors are listed now. We could have a function for calling just these types of contributors and leaving out other types.
- Contibutors belonging to a userGroup marked as "Translator" would be listed in the landing page with the given UserGroupName mentioned after the Contributor name and shown according to the standards defined in citation styles and different metadata schemas.
- Contibutors belonging to a userGroup marked as "Other" would *only* be listed in the landing page with the given UserGroupName mentioned after the Contributor name. This type could be used for all kinds of contributors that do not need to be mentioned in metadata exports, like illustrators, photographers etc.
Feel free to add additional comments there too, if you’d like.
I think there will be a desire to integrate the CASRAI standard as noted in this issue for future versions too. Like you, I too would be curious if folks have found a work arounds.
-Roger
lsteele
February 16, 2022, 9:05am
#3
Hi Roger,