related links using `doi` over `recid` is not comfortable whilst developing

[tiborsimko]

Current behaviour

When developing new records locally, such as ATLAS HEPMC records from cernopendata/data-curation#259, and when one introduces relations between new records of this kind:

    "relations": [
      {
        "description": "For citing all the 13 TeV HEPMC data, and to find other related datasets, please see",
        "doi": "160000",
        "recid": "10.7483/OPENDATA.ATLAS.XPJL.4L42",
        "title": "HEPMC format 13 TeV proton-proton Open Data from the ATLAS experiment",
        "type": "isChildOf"
      }
    ],

then the linking of the records is happening via DOI (which is not yet minted) rather than via record ID:

This has two problems:

• the "Parent Dataset" button is not clickable, or better said it does not lead to parent records;
• the "Related datasets" box displays "None" and does not provide links to the parent record.

This makes local development less comfortable, since it's harder to check whether links are OK.

Moreover, if the record is displayed on QA for perusing by theorists, the beta testers of the records may report bad links.

Expected behaviour

When the DOI is not minted, the record ID should be used for links.

Alternatively, we could always prefer using record IDs rather than DOIs for internal links.

[dianarand]

Tried to reproduce the issue locally by inserting records to my local instance with recid 80017 and 80020 after deleting the "doi" part of the relation. Looking at record with recid 80017, both the link on the parent dataset and the link under related dataset are displayed correctly and work as intended.

More details in regards to this issue would be appreciated.