Include additional fields to manifest

[jorgee]

Include new fields in the manifest and update the documentation with the new fields

[netlify]

✅ Deploy Preview for nextflow-docs-staging ready!

Name	Link
🔨 Latest commit	bcc6524
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-docs-staging/deploys/66ec2aca8b83110008ef3aa5
😎 Deploy Preview	https://deploy-preview-5314--nextflow-docs-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[pditommaso]

Looks neat. Thin @ewels was suggesting to user icon instead of iconUrl in a recent comment

[jorgee]

Looks neat. Thin @ewels was suggesting to user icon instead of iconUrl in a recent comment

Yes, changed.

[pditommaso]

Well done! 🎉

[ewels]

Ooh awesome! Thanks @jorgee!

Looks like author / maintainer fields are just strings here. Could we optionally have these as maps as well with additional subfields such as ORCiD, affiliatiob and email? See #4034 (comment)

'cc @pditommaso @bentsherman

[pditommaso]

Think we said it would be better to keep it flat

[bentsherman]

The BCO supports a bunch of contributor metadata as a list of maps, so you can do something like name, email, ORCID

https://wiki.biocomputeobject.org/Provenance-domain#Contributors_%E2%80%9Ccontributors%E2%80%9D

I think we could support this structure directly in the config. The manifest.author could be either a string for comma-separated list, or a list of maps for the complete structure. I think name, affiliation, email, and ORCID should be enough, but always easy to add more fields later.

See also: nextflow-io/nf-prov#10

[bentsherman]

So the list of maps is mainly to provide a more complete BCO manifest

[jorgee]

In fact, there is no check in the author, so you can put whatever valid expression (String, list, list of maps).

manifest {
     author = [ [ name: 'First Author', email: 'author1@mail.com'], [ name: 'Second Author', email: 'author@mail.com']]
}

The above configuration should work. In the nextflow info, it will print the string serialization of the list of maps.
I think we just need to validate the map fields.

[ewels]

Nice! Yes some validation would be nice just to provide a base level of standardisation.

Though saying that, it could be nice to allow additional arbitrary keys - eg. GitHub handle or I'm sure there are others.

[ewels]

Ok so if it already works, shall we say that a short term solution is to just modify the documentation to say that it can be a string or a map? Sounds like that would be sufficient for now. We can standardise on nf-core and come back to this if needed.

[ewels]

👉🏻 #5316