Within metadata default-3, within the 'creator' type only, the "Author identifier (Scopus)" requires a "name_identifier" of 11 numbers when there are identifiers available with just 10 numbers (for example https://www.scopus.com/authid/detail.uri?authorId=8375574300). Anything of lower than 11 is not allowed as an answer field and will not be saved. When converting from default 2 to default 3 within the webportal, an error will be thrown that conversion is also not possible.
For contributor types, the number length is not enforced and is allowed to be saved when numbers are less than 11.
Expected Behavior
Allow Author ID to be 10 numbers for creator types.
Steps To Reproduce
Open Yoda metadata default 3.
Add creator with "Name_Identifier_Scheme": "Author identifier (Scopus)".
Try to add 10 numbers and save.
(or create a default 2 scheme, add creator with author ID scopus and add 10 numbers, then convert to default 3)
Is there an existing issue for this?
Current Behavior
Within metadata default-3, within the 'creator' type only, the "Author identifier (Scopus)" requires a "name_identifier" of 11 numbers when there are identifiers available with just 10 numbers (for example https://www.scopus.com/authid/detail.uri?authorId=8375574300). Anything of lower than 11 is not allowed as an answer field and will not be saved. When converting from default 2 to default 3 within the webportal, an error will be thrown that conversion is also not possible. For contributor types, the number length is not enforced and is allowed to be saved when numbers are less than 11.
Expected Behavior
Allow Author ID to be 10 numbers for creator types.
Steps To Reproduce
Open Yoda metadata default 3. Add creator with "Name_Identifier_Scheme": "Author identifier (Scopus)". Try to add 10 numbers and save. (or create a default 2 scheme, add creator with author ID scopus and add 10 numbers, then convert to default 3)
Environment