jzichichi
commented
5 years ago @aergul According to requirement above, "Publisher should be a plain text element with minimal validation - it must have some value, but any value is acceptable." It looks like current validation requires more than just "any value", since it doesn't like just "Jessica"
Publishing Organization seems to have the same rules but I don't see anything specific for that element listed above. @torrin47 - for publishing organization, should this be a defined list or is it free text well?
email looks OK
torrin47
aergul
The project open data schema allows a publisher element to be a nested object: https://project-open-data.cio.gov/v1.1/schema/#publisher we've never offered that option to EPA audiences, and they've never requested it, so I'm inclined to make this element a plain text string in the MVP, and postpone further flexibility as an optional enhancement down the road.
Publisher should be a plain text element with minimal validation - it must have some value, but any value is acceptable. Publisher email must validate with email address syntax.
If and when we implement ORCID authentication, all of these elements should be pulled from the ORCID API - though we'll want to explore the implications of that option. Presumably we'll need to allow the user to select from multiple possible organizations and name and email variants as well as edit the values after they're populated.