| Issue Number | 612 |
|---|---|
| Summary | Representation of related articles is not clear |
| Created | 2021-09-09 10:05:15 |
| Issue Type | Improvement |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2022-12-12 09:48:54 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.298233 |
Suppose you are viewing article A and you add a relationship to indicate that A is a duplicate of article B. Then you bring up the page to view article B and you see that A is a related article for this article, though there is no indication as to which article is on which end of the linking relationship (in this case, which article is the duplicate, and which the original). You bring up the form to edit this relationship and you see that the RELATED ARTICLE ID field is populated with the ID of article B, the article you have been viewing. Article A, from which the relationship link was created, is stored in a hidden field, and is nowhere visible on the form. Furthermore, the language describing the values for the field immediately below for RELATIONSHIP TYPE say things like "this article has a ..." where presumably "this article" means article A, which is not identified on the form. Wouldn't it be better to say "Article A has a ..." (where "A" is replaced by the ID of the linking article in the relationships)? Also, shouldn't "has a ..." be changed to "has one or more ..." since on the original form the first field allows for the entry of multiple linked article IDs?
The incentive for filing this ticket is largely driven by the need to get the data structures (and their property names) right for the Drupal 9 rewrite of the EBMS.
In EBMS4, when you are viewing the full history page for an article,
and you click the Related button to identify other articles which are
related to this one, those other articles are recorded in the
related column of
the ebms_article_relationship table, and the article you
are viewing is recorded in the related_to column of that
table.
We want to keep the task of linking related articles as simple as possible, so we'd like to keep the relationship between articles at the current level, rather than designate which article is the main article and which is the editorial/comment. Just knowing that they are related is all we need at this time.
Elapsed: 0:00:00.000737