Create interconnected FAIR-DOs

[maximiliani]

Relationship management API

see issue #109

Why?

While creating a more complex use case of FAIR-DOs, I needed to create connected FAIR-DOs. The Typed PID Maker couldn't do it, therefore I initially planned to write a (highly disposable) Python script. Until I saw this open issue...

In issue #109 an idea of managing relationships of already existing FAIR-DOs was introduced. This was not quite what I needed for my use case, because I had to create a not small amount of FAIR-DOs (>2500 per data source --> 3*2500 = 7.500 FAIR-DOs). This made it undesirable to first create some half-finished FAIR-DOs, just to extend them later... Therefore, I extended the existing /pit/pid endpoint to create connected FAIR-DOs from a list of PIDRecords with "fantasy PIDs" just for referencing. These "fantasy PIDs" are mapped to freshly-generated PIDs and simply replaced in the value fields of all the records in the same request.

What?

• create POST /api/v1/pit/pids endpoint for creating connected FAIR-DOS
  • accept a list of PIDRecords with "fantasy PIDs" that are referenced in other PIDRecords values and simply replace them
  • OpenAPI v3 documentation
  • add implementation for createPIDs() method
  • Testing

See future ideas in issue #109

[Pfeil]

Note: bidirectional relations should be properly defined. Some bidirectional relations have different relation types. For example, "hasMetadata" and "isMetadataFor". Should / can we (reliably) support these cases?

[maximiliani]

Note: bidirectional relations should be properly defined. Some bidirectional relations have different relation types. For example, "hasMetadata" and "isMetadataFor". Should / can we (reliably) support these cases?

Probably, this would be useful at some point in time. For now, due to time constraints and a lack of a concrete use case, I moved these ideas to the original issue (#109).