For secondary ids it seems to be sensible to allow also for a local ID. This might come in handy if inconsistencies are spotted at some aggregator etc.
Note that in join2 the base-records for contracts are shared amongst all partners. IOW all join2 partners have the same, common record for the DEAL contracts etc. (join2 shares those records vai OAI.) Now, the very same record is used in e.g. Jülich, DESY, DKFZ while the costs returned by either instance vary depending on the source of delivery. Effectively, every join2 instance could provide costs for all partners, but this has to be transparent for openCost. (Here it explicitly makes sense to be able to differentiate by some local ID.)
For secondary ids it seems to be sensible to allow also for a local ID. This might come in handy if inconsistencies are spotted at some aggregator etc.
Note that in join2 the base-records for contracts are shared amongst all partners. IOW all join2 partners have the same, common record for the DEAL contracts etc. (join2 shares those records vai OAI.) Now, the very same record is used in e.g. Jülich, DESY, DKFZ while the costs returned by either instance vary depending on the source of delivery. Effectively, every join2 instance could provide costs for all partners, but this has to be transparent for openCost. (Here it explicitly makes sense to be able to differentiate by some local ID.)