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

Add Person Involved information entity (like Whistleblower Identity) #1339

Open
fpietrosanti opened this issue Jul 27, 2015 · 4 comments
Open

Comments

@fpietrosanti
Copy link
Contributor

fpietrosanti commented Jul 27, 2015

This ticket is to improve the quality of the structure of the submissions being done by whistleblower with the regards to "Persons Involved".

This shall be a special group-field type "Person Involved", that include a number of free-text and structured fields to qualify who are the persons being involved in the facts being reported, which is their level of involvement, how much do they know about the issue, if they can be contacted to help with the investigation asking them some questions or it's better to avoid contacting them at all.

The Whistleblower shall be able to indicate multiple persons involved, clicking "Add new person" .

The Receiver shall be able to view the persons involved in a structured way on the tip interface, not just as a part of the standard questions answered.

The admin shall be able, like for the Whistleblower identity at #185 to:

  1. view/enable/disable/change each default persons involved field
  2. add new persons involved field
  3. title text: Title of the box asking the Persons involved (by default "Persons involved")
  4. prefix text: The text to be displayed/customized as an introduction before asking for the persons involved
@evilaliv3
Copy link
Member

@fpietrosanti in relation to what partially specified i've the following doubt:

  1. for what concerns different regulations each country may have specific questions (e.g. C.F. / P.IVA? ID Number). How to deal with such differencies? Its not even simple that we can do fields for different languages because an italian man filling an italian form would want to add info of a person in taiwan.
  2. you specified the prefix texts; each field by design has the possibility to use a "description" and an "hint. so the prefix text is exactly the description.

@fpietrosanti
Copy link
Contributor Author

@evilaliv3

  1. It's in the "Whistleblower Identity" that may require a "tax ID" that may differs, but not on "Persons Involved" where the WB is not expected to know their tax-code, so i think that we don't have cross-country issues.
    Btw giving the ability to "1. view/enable/disable/change each default persons involved field" + "2. add new persons involved field" we should be ok with a good default, and ability to customize it finely (within reasonable limits)

  2. Graphically the "Persons involved" sections is a section, where the WB is expected to add persons involved, like for Whistleblower Identity Management Feature #185, that shall stay in a visually delimited area.
    That section (that's within a step that's within a context) that we call "Persons Involved" contain the "Persons Involved" items.
    Obviously being a section, visually/UX-logically separated from the other submission fields in the same step, it should have a Title and a Text Prefix to be displayed before starting adding "Persons Involved".

It can be a "description" if technically the information element "Person Involved" is a Group Field.

Btw for OpenWhistleblowing that's low-priority compared to WhistleblowerIdentity & Custodian sketch up.

@evilaliv3
Copy link
Member

evilaliv3 commented Jul 28, 2015 via email

@evilaliv3 evilaliv3 added this to the 2015 September milestone Sep 21, 2015
@evilaliv3
Copy link
Member

@fpietrosanti can you take care of studying the texts to be put in this field on the line of the work done for #185?

this way i will be able to proceed on this ticket.

@evilaliv3 evilaliv3 modified the milestones: 2015 October, 2015 September Oct 6, 2015
@evilaliv3 evilaliv3 modified the milestones: 2015 November, 2015 October Nov 2, 2015
@evilaliv3 evilaliv3 removed this from the 2015 November milestone Dec 7, 2015
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

2 participants