Make naming a contributor in a session automatically create a corresponding Person in the People list

[nthieberger]

When a person is created in a session they are not then available in the people list. I think they should be. Version 0.8.4

[hatton]

@nthieberger Can I ask for your help understanding more about what we want here?

When the contributions are for things like Speaker, Signer, or Singer, then it's obvious that these are also "Person"s in lameta because we need some info about them, like age, and also consent from them. In other requests, I'm told that we need the program to ensure that we have gathered this info by, for example, refusing to export IMDI if they are missing.

Then I look at the full list of contributor roles: "Annotator, Author, Careful Speech Speaker, Compiler, Consultant, Data Inputter, Depositor, Developer, Editor, Illustrator, Interpreter, Interviewer, Participant, Performer, Photographer, Recorder, Researcher, Research Participant, Responder, Signer, Singer, Speaker, Sponsor, Transcriber, Translator". And I wonder, why would I need the age of a consultant, a depositor, etc? Do I need a consent form from an Editor?

I'm concerned that making a Person out of each contributor, automatically, will have a cost that I think people will find annoying, e.g. asking some colleague (who is not part of the language community) for their age and a consent form in order to "satisfy this demanding software".

I can imagine several responses, among them:

1. Yes, you do need all that. If you touched the deposit, then we need your info and record of your consent.
2. No, but it's simpler to just tick all the boxes for everyone rather than make exceptions based on role
3. This problem hasn't really come up before because we weren't using software that we're asking to enforce rules like this. If a human archivist was looking, they'd distinguish between what is needed for each person by the role they played.

Thanks for your help!

[HughP]

One way forward here is to use events to control roles. Assign roles to specific event types and then certain types of events license roles and documentation requirements. All the best, -Hugh

…

Sent from my iPhone

On Mon, Dec 18, 2023 at 5:46 AM John Hatton ***@***.***> wrote: @nthieberger <https://github.com/nthieberger> Can I ask for your help understanding more about what we want here? When the contributions are for things like Speaker, Signer, or Singer, then it's obvious that these are also "Person"s in lameta because we need some info about them, like age, and also consent from them. In other requests, I'm told that we need the program to ensure that we have gathered this info by, for example, refusing to export IMDI if they are missing. Then I look at the full list of contributor roles: "Annotator, Author, Careful Speech Speaker, Compiler, Consultant, Data Inputter, Depositor, Developer, Editor, Illustrator, Interpreter, Interviewer, Participant, Performer, Photographer, Recorder, Researcher, Research Participant, Responder, Signer, Singer, Speaker, Sponsor, Transcriber, Translator". And I wonder, why would I need the age of a consultant, a depositor, etc? Do I need a consent form from an Editor? I'm concerned that making a Person out of each contributor, automatically, will have a cost that I think people will find annoying, e.g. asking some colleague (who is not part of the language community) for their age and a consent form in order to "satisfy this demanding software". I can imagine several responses, among them: 1. Yes, you do need all that. If you touched the deposit, then we need your info and record of your consent. 2. No, but it's simpler to just tick all the boxes for everyone rather than make exceptions based on role 3. This problem hasn't really come up before because we weren't using software that we're asking to enforce rules like this. If a human archivist was looking, they'd distinguish between what is needed for each person by the role they played. Thanks for your help! — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJ2JVOTNYDD7JNSOPSFBDYKBCJ7AVCNFSM4LBKPUNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWGA2TIMZWGEZQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[nthieberger]

Can the name can just be added to the people list without any further details? If you have a a number of items to describe it would be easier if the name appeared in the dropdown. Currently, if you add a name to an item, it is not then avilable for he next item

[hatton]

Yes, you're right, that's how it should work. Let me look into that.

[hatton]

Working on this for lameta 2.3

[hatton]

In the end, here's what we did for lameta 2.3:

1. When you're typing in a name that isn't matching a Person record, you see a ❓
2. When a name that doesn't have a matching Person record is shown in a list, you also see the ❓after their name:

3. Finally, contributors without matching Person records also get this icon in the list of choices: