search

EQAR / eqar_frontend

(archived - see new repository deqar_frontend) ReactJS admin frontend for the DEQAR database.
https://github.com/EQAR/deqar_frontend
0 stars 0 forks source link

Report form updated design - all modes #136

Open Gyukat opened 5 years ago

Gyukat commented 5 years ago

Below I will attach five the newly proposed report form in five modes, on five separate JPG files:

  1. Report webform
  2. Report edit webform
  3. Report view
  4. Report edit webform (Admin)
  5. Report view (Admin)

As you will see these are effectively the same form presented for data entry, editing and viewing for both agency users and for admin users. For each of the modes, I have given several "screen shots" presenting different situations. I have tried to cover many different situations in this visual way, which I hope will reduce the need for lengthy written explanation report webform_2019-01-08 report edit webform_2019-01-08 report view_2019-01-08 report edit webform admin_2019-01-08 report view admin_2019-01-08

.

Gyukat commented 5 years ago

I have included a Record Management box on the view and edit modes. I have given a choice of three different basic designs; you can use any of these---whatever looks best and keeps the save/edit button accessible without scrolling.

As mentioned to Josh on our call last week, it is important that the institution and programme fields are presented in alignment with the activity type. In other words, if the activity is type: "institutional", then we should not present programme fields/buttons at all. If the activity is type: "joint programme", we should present/require multiple institution entries but only make one programme entry, etc.

The save button should be activated only when the new/edited record has all the required data for that proposed activity type. (We discussed highlighting required fields in red, but it is not clear that this is needed...so you can hold off on it for now.)

Buttons and "X" are used to move from page to page, including some pop-ups; linked text in CAPS is used to display repeated fields. Other linked text is used for internal/external linking within the records. (This linked text is generally strings created from concatenating values in the source record. We can discuss the format of each of these OR you can simply try what you think is best.) There is also one link to the institution menu pop up view through the institution data entry box. If it is not clear, please feel free to ask me what the links are for.

Gyukat commented 5 years ago

browse report standard list_2019-01-09 browse report agency list_2019-01-09

Gyukat commented 5 years ago

These are the two Report Browse Lists/Menus.

The first is a page under "Reference Data": 'Reports', Institutions, Countries, Agencies and gives an overview of all reports uploaded by agencies in the system. It is linked to the second report browse list at the bottom left of the page.

The second is the main page of "My Agency" and has a button to Add New record, which takes you to Submit Report: Report Form.

p.s. We should probably move the ADD NEW institution button to the right side as well. It is more intuitive there.

Gyukat commented 5 years ago

By the way the two lists have some slight differences in the data listed...

  1. agency v. upload date
  2. activity type v. activity (the second is ONLY the activities of the particular agency of course)

Other things to note:

Gyukat commented 5 years ago

Content fields that need to be added to the Report in DM:

Content table that need to be added to the Report in DM:

Administrative field that need to be added to the Report in DM:

JoshBone commented 5 years ago

Content fields that need to be added to the Report in DM:

  • Comment
  • NEW! Narrative Report Summary

Content table that need to be added to the Report in DM:

  • Partner Agency

Administrative field that need to be added to the Report in DM:

  • Event Tracking <date/time stamp> >> on "save record"
  • Event Tracking Note
  • Internal Note

I would rather put this as a new issue to the backend, because it's closely related to that. https://github.com/EQAR/eqar_backend/issues/272