amy icon indicating copy to clipboard operation
amy copied to clipboard

Feature Request- Add task = add person

Open Talishask opened this issue 6 years ago • 6 comments

Creating this issue based on a recent email from Giacomo: Long standing issue: when we add a task (a person) to a workshop, if the person is not already in the DB, we need to move to the ‘add person’ form, add the person there, return to the workshop, add the task.

This might have had sense when we were aspiring at having a detailed profile of any person in the database. However, since we are more and more often adding persons with just their names, I wonder if a way could be implemented so that adding a new task (person) to a workshop, automatically add the person in the database!

Talisha: I too experience this issue. I'm currently using a text editor as a work around.

Talishask avatar Oct 22 '19 13:10 Talishask

~~The strange thing is that the code is supposed to create a new person when there's no match from DB.~~

~~I think this is a bug and I may need a sample input CSV file that doesn't allow to create persons.~~

EDIT: I misunderstood Giacomo. I thought he had meant the bulk upload feature. In case of changing add task form, it's not a bug - it's a feature! I'll provide timespan required for me to implement this change.

pbanaszkiewicz avatar Nov 07 '19 19:11 pbanaszkiewicz

Update on the feature request: I will need to know if you want to ditch the old interface ("person", "role", instructor training seats) and use only the new one ("person name", "person last name", "person email", "role", instructor training seats), or combine both ways of adding a task.

pbanaszkiewicz avatar Nov 07 '19 19:11 pbanaszkiewicz

@pbanaszkiewicz can you clarify what you mean by the old and new interface?

maneesha avatar Jan 14 '20 14:01 maneesha

@maneesha when adding a task to the workshop you have these fields: obraz

This is the current ("old") interface. It assumes a person already exists for this task.

But @gperu & @Talishask want to add tasks when persons don't exist, which means we have to create them. So in the "new" interface we'd have to replace "Person" field with three fields required to create a person: personal name, family name, and their email. However, if we do that, we lose that "old" functionality to add a task for existing person.

Here's what I need to know: how do you see this implemented?

pbanaszkiewicz avatar Jan 14 '20 16:01 pbanaszkiewicz

Hi @pbanaszkiewicz ,

We enter tasks at two points in our workflow, when we are notified about the workshop and create the event and after the event has occurred.

Currently, when a person is not in the database we need to:

  • Open 'New Person' in a new window
  • Add the individual's information and submit the person
  • Return to the event edit page
  • Add task in the event We have found a workaround to this by recording information for persons not already in AMY in a csv for bulk upload. It's still additional work but not as tedious as adding the person each time.

We would still hope to have the current functionality to add a task for an existing person, but if the person is not in AMY we need to add the person into AMY in order to add the task. More frequently, we are adding individuals without an email address. So we are hoping that the add a task function would also allow us to add a person if the person is not currently in the database. When adding a task, would it be possible to:

  • have the 'Person*' field function the same, but if the name is not recognized a 'New Person?' option appears in the list?
  • then when we select 'New Person?' three fields pop up under the 'Person*' field for us to add the information for the new person (Personal (first) name*, Family (last) name, and Email address)
  • When we press submit it creates the person and adds the task

not sure if that's an option or but maybe?

Talishask avatar Jan 17 '20 17:01 Talishask

Making a note here as I discussed this with @fmichonneau Right now we have consents for when someone manages their own profile. We will also need to modify our privacy policy to note conditions where we may create a profile for someone.

maneesha avatar May 04 '22 18:05 maneesha

Closing this here and will consider the issue of consents separately.

maneesha avatar Apr 11 '23 14:04 maneesha