Make use of system-specific fields

[Pfeil]

Is your feature request related to a problem? Please describe.

For different PID records, we may want to have the URL field of the Handle System to be filled using a value of a different type. It may be the digitalObjectLocation for many, but for some it may be a landing page or so.

Describe the solution you'd like

When doing a request, I want to specify the URL field. Either in the JSON input, or as a URL parameter.

Additional context

• as an optional parameter, this would not be a breaking change
• the current way (having a fixed configuration) would stay as the default in order to not break functionality
• For other systems than the handle system, this may be ignored.
• This is somehow related to Validation on resolution of PIDs may indicate errors in record due to non-resolvable fields #253 , where I suggest to ignore URL fields. If we ignore them, the parameter should not be part of the usual attributes as input as well. If we allow it though and validation may ignore it, we could do it here, too. In order to not complicate things, I propose a url parameter like "?copyRedirectUrlFrom=$attributePID" or similar.

[Pfeil]

@maximiliani @nicolasblumenroehr just wanted to ask early for your opinion on this.

• Any ideas on the parameter name or the solution?
• Any other special handle fields we have in mind?
• I would not touch administrative things like ACL or so, but something a lot of people may want in their records. If the URL field is the currently only one, I'd rename the issue accordingly :D
• Also, I think it is a good idea to stick with the "any information we put into special fields is a copy of a typed attribute" where it makes sense.

[maximiliani]

I agree, no other attributes come to my mind right now.