-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comments
@enwardy are you able to elaborate on this requirement? 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? |
Each party identifier needs to have a type to specify. Only one identifier for each type. Multiple identifiers of different types for each person. Needed mostly for collectors though there may be other use cases.
… On 23 Jan 2017, at 4:16 pm, JonoGillett ***@***.***> wrote:
@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?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ok, so to clarify:
Does that sound right? |
I think that is correct but we should verify with Nick Ward
… On 23 Jan 2017, at 5:35 pm, JonoGillett ***@***.***> wrote:
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?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yes, that is correct. |
still outstanding, but not sure now about Priority level of this (perhaps not #1) |
@nthieberger is this still relevant? |
to allow for different types of party identifiers (e.g. NLA, ORCID) to be recorded
The text was updated successfully, but these errors were encountered: