Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding additional 'Party Identifier' fields for a Collector #608

Open
enwardy opened this issue Nov 17, 2016 · 7 comments
Open

adding additional 'Party Identifier' fields for a Collector #608

enwardy opened this issue Nov 17, 2016 · 7 comments

Comments

@enwardy
Copy link

enwardy commented Nov 17, 2016

to allow for different types of party identifiers (e.g. NLA, ORCID) to be recorded

@JonoGillett
Copy link
Contributor

@enwardy are you able to elaborate on this requirement?
Given that users in the system already have a 'party identifier' attribute, my reading of this task is that you want to allow multiple 'party identifiers' (but only when the user is a collector) - is that correct?

You've also mentioned 'types' - are those simply possible values which could be added to the one 'party identifiers' list, or are they separate categories of party identifiers each of which can contain more than one identifier?

@LindaBarwick
Copy link

LindaBarwick commented Jan 23, 2017 via email

@JonoGillett
Copy link
Contributor

Ok, so to clarify:

  • there are multiple types of identifiers (ORCID, NLA etc - and presumably we want the ability to add more later?)
  • each user can optionally have one identifier of each type (but not multiple for the same type)
  • we don't want to restrict this behaviour just to collectors

Does that sound right?

@LindaBarwick
Copy link

LindaBarwick commented Jan 23, 2017 via email

@enwardy
Copy link
Author

enwardy commented Jan 23, 2017

Yes, that is correct.

@enwardy
Copy link
Author

enwardy commented Feb 14, 2018

still outstanding, but not sure now about Priority level of this (perhaps not #1)

@johnf
Copy link
Member

johnf commented May 8, 2024

@nthieberger is this still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants