-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
Introduce an "Evidence" special field type containing file upload along with meta data #1364
Comments
@fpietrosanti We support that! In addition there is a problem with current file upload function #1373. |
I like this feature a lot but we don't currently need it for Publeaks. |
ok @marceloomens; this was simply a mistake of @fpietrosanti that simply labeled it so as we probably discussed it during the hackaton with some of the UI experts. |
Marcel, isn't that the way GoldiLocks has specified the UX for the Tip page of Whistleblower?
Fabio
Sent from mobile
|
I'd suggest to check how the Tip page has been reworked by GoldiLocks, as it's not yet in the frontend developed prototype but it's done that way in the wireframe design afaik.
Sent from mobile
|
@fpietrosanti You're right actually, see the screenshot below: At the same time I suggest we give this the lowest priority. The regular tip submission workflow doesn't allow whistleblowers to add comments etc. to individual files and I don't expect this to be a popular and often-used features. |
ok for lowering the priorities with respect of Publeaks where it is not a requirement. anyhow the regular tip workflow will allow such a possibility in the short term given requirements we have in other projects so you can keep in mind to switch using it if you want. |
This ticket is to implement the default special field type "Evidence" so that by default there will not be anymore just a single file upload, but an "Evidence" field that's more rich than just a file upload.
The Evidence provided by default is also to be visualized in the Tip page with the enriched meta-data (ie: description and a selector for each kind of file).
That has to be implemented as a special type of FieldGroup, part of the default field database.
This is also maybe related to #1239
The text was updated successfully, but these errors were encountered: