You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Information specified by the related_to_table_dois and related_to_hepdata_records fields is not currently rendered when a record is in preparation and has not yet been finalised, probably because of the changes made in PR #732 to improve the linking of records/tables for records with multiple versions. This makes it difficult for submitters to know if they have specified these fields correctly, leading to situations like https://www.hepdata.net/record/ins2729396?version=1 where duplicate links appear because the bidirectional links have been specified both ways in the encoding. The following changes should be made:
The related_to_table_dois links in the forward direction should always be shown irrespective of whether the two related records are in preparation or finalised.
The related_to_table_dois links in the backward direction should be shown if the records containing the referring tables have been finalised or if the referring tables are in the same record (which might not be finalised).
The related_to_hepdata_records links in the forward direction should always be shown irrespective of whether the two related records are in preparation or finalised.
The related_to_hepdata_records links in the backward direction should only be shown if the most recent versions of the referring records have been finalised.
Could you please look into these issues, @ItIsJordan?
The text was updated successfully, but these errors were encountered:
Implements a number of changes listed in #796 to forward relations ( which now appear even if relating object is not finished). As well as changes in the backwards direction, to allow tables within the same HEPSubmission to reference another in the same one.
Information specified by the
related_to_table_dois
andrelated_to_hepdata_records
fields is not currently rendered when a record is in preparation and has not yet been finalised, probably because of the changes made in PR #732 to improve the linking of records/tables for records with multiple versions. This makes it difficult for submitters to know if they have specified these fields correctly, leading to situations like https://www.hepdata.net/record/ins2729396?version=1 where duplicate links appear because the bidirectional links have been specified both ways in the encoding. The following changes should be made:related_to_table_dois
links in the forward direction should always be shown irrespective of whether the two related records are in preparation or finalised.related_to_table_dois
links in the backward direction should be shown if the records containing the referring tables have been finalised or if the referring tables are in the same record (which might not be finalised).related_to_hepdata_records
links in the forward direction should always be shown irrespective of whether the two related records are in preparation or finalised.related_to_hepdata_records
links in the backward direction should only be shown if the most recent versions of the referring records have been finalised.Could you please look into these issues, @ItIsJordan?
The text was updated successfully, but these errors were encountered: