EQAR / deqar_frontend

Version 2 of the DEQAR Admin Interface, with create-react-app v2, refreshed 3rd party libraries, and many more...
0 stars 0 forks source link

Report Module #3

Closed Gyukat closed 3 years ago

Gyukat commented 5 years ago

https://github.com/EQAR/eqar_frontend/issues/136?_pjax=%23js-repo-pjax-container

Gyukat commented 5 years ago

TESTING MANUAL REPORT SUBMISSION:

Institution / Programme Assignment:

File Assignment:

Other:

Submission:

Gyukat commented 5 years ago

TESTING REPORT RECORD VIEW:

Visual Problems:

Other:

JoshBone commented 5 years ago
  • if you browse for a file, and then want to cancel the option, it is not possible.

Currently it's working in a way, that you have to select browse and then press cancel. Should I include a cancel button somewhere?

But just to clarify, you want to cancel, if you accidentally selected a file and you rather want to enter a URL. Because otherwise, you should press X on the main form to remove the file and save the record.

YES...TRUE

JoshBone commented 5 years ago

long file names still go off the end of the pop up box.

Can you post a screenshot?

JoshBone commented 5 years ago

not sure what should happen when you successfully submit, but intuitively I would expect to be taken back to the list and to SEE my new report in the list. Then I would happily do the next entry (Currently, you have some very nice messages, which show both the record being created and the file being uploaded. These should definitely STAY. BUT after this, you are presented with empty record.)

Should we jump to the list page, or rather show the newly created record (with the flags and dates) in 'view' mode?

Gyukat commented 5 years ago

long file names still go off the end of the pop up box.

Can you post a screenshot?

screen shot 2019-03-03 at 20 00 44
Gyukat commented 5 years ago

not sure what should happen when you successfully submit, but intuitively I would expect to be taken back to the list and to SEE my new report in the list. Then I would happily do the next entry (Currently, you have some very nice messages, which show both the record being created and the file being uploaded. These should definitely STAY. BUT after this, you are presented with empty record.)

Should we jump to the list page, or rather show the newly created record (with the flags and dates) in 'view' mode?

I guess that I would be open to either. It would be nice to add a "New record" button on either the record or the menu...otherwise, are we depending on the user to use the side menu?

MOVE BUTTON TO THE RIGHT SIDE

Gyukat commented 5 years ago

NEW THINGS: SIDE MENU

MENU (My Uploaded Reports)

Gyukat commented 5 years ago

REPORT RECORD

GENERAL

VIEW

CREATE

EDIT

ADMIN EDIT

JoshBone commented 5 years ago

Why did you combine the uploaded reports and submission under My Reports? I preferred it separate.

I thought that it looks a bit more organised, but define the menu how you would like to see, and that's how it's going to happen...

JoshBone commented 5 years ago

What is the difference between the Menu under My Agencies and My Uploaded Reports? I don't think the first has much to do with Agencies and there is a neat according feature on the first that I don't see on the second.

I guess My Agencies will have the form where you can actually edit the information about agencies that belonging to your user.

JoshBone commented 5 years ago

I think the date filters can be by year only. This will save space and be more intuitive. You can put YYYY in the filter boxes to clarify. The uploaded date column can be narrower, by either removing the time or by putting it on the second line.

You mean by removing the active checkbox? - I've spent quite some time to implement it... :)

JoshBone commented 5 years ago

I still don't like the field boundaries. It looks like you should enter something. Are you worried about the aesthetics if we get rid of the boundaries? Is there no way to make it look nice and also simply be "flat" data on a white background. (in the very least make the field background pure white.)

The thing is that the data is the same form-data. I think it looks much nicer that you can change the view when you edit, and you just have to enter the data into real fields... I can make all kinds of styles, lighter border, lighter text color, but still want to keep them as fields.

JoshBone commented 5 years ago

When you use the browse, we still get the "file location was not provided" note and yellow flag on the notification but not in the system.

This won't be the case, when we have the email digesting method. (After I come back from SA)

JoshBone commented 5 years ago

Does this exist? Where can I add internal notes/comments? Where can I deactivate flags?

Not yet. Should this be some separate admin menu, or rather the same report list (Reference Data -> Reports) should have editing options if the user has admin privileges?

JoshBone commented 5 years ago

Flagging column can be narrower by changing drop down to none, low, high. The flags themselves can also read "low" and "high". The column can be labelled Flag Level.

Can I change this system (frontend + backend) wise? So that it will affect everything? (Outgoing email, and stuff)

Gyukat commented 5 years ago

What is the difference between the Menu under My Agencies and My Uploaded Reports? I don't think the first has much to do with Agencies and there is a neat according feature on the first that I don't see on the second.

I guess My Agencies will have the form where you can actually edit the information about agencies that belonging to your user.

But the accordion feature is super neat...can't we use it in My Uploaded Reports and Reference Reports or is it too "busy"?

Gyukat commented 5 years ago

I think the date filters can be by year only. This will save space and be more intuitive. You can put YYYY in the filter boxes to clarify. The uploaded date column can be narrower, by either removing the time or by putting it on the second line.

You mean by removing the active checkbox? - I've spent quite some time to implement it... :)

No, keep the checkbox...it is cool. I mean that in the field itself allow the year. It should be enough to filter and is cleaner and takes less space.

Gyukat commented 5 years ago

I still don't like the field boundaries. It looks like you should enter something. Are you worried about the aesthetics if we get rid of the boundaries? Is there no way to make it look nice and also simply be "flat" data on a white background. (in the very least make the field background pure white.)

The thing is that the data is the same form-data. I think it looks much nicer that you can change the view when you edit, and you just have to enter the data into real fields... I can make all kinds of styles, lighter border, lighter text color, but still want to keep them as fields.

Well, then, make the background white and quite light or checked borders.

Gyukat commented 5 years ago

Does this exist? Where can I add internal notes/comments? Where can I deactivate flags?

Not yet. Should this be some separate admin menu, or rather the same report list (Reference Data -> Reports) should have editing options if the user has admin privileges?

I was thinking the latter...any opinions?

Gyukat commented 5 years ago

Flagging column can be narrower by changing drop down to none, low, high. The flags themselves can also read "low" and "high". The column can be labelled Flag Level.

Can I change this system (frontend + backend) wise? So that it will affect everything? (Outgoing email, and stuff)

I would think it would be fine, as long as the labels are changed to read "flag level" in every instance.

IN FACT JUST SAY "FLAG" IN THE LABEL AND THEN USE SIMPLY: HIGH, LOW, NONE. IT IS MUCH SIMPLER!!!

Gyukat commented 5 years ago

Why did you combine the uploaded reports and submission under My Reports? I preferred it separate.

I thought that it looks a bit more organised, but define the menu how you would like to see, and that's how it's going to happen...

I like:

MY DATA

MENU

JoshBone commented 5 years ago

I think the date filters can be by year only. This will save space and be more intuitive. You can put YYYY in the filter boxes to clarify. The uploaded date column can be narrower, by either removing the time or by putting it on the second line.

You mean by removing the active checkbox? - I've spent quite some time to implement it... :)

No, keep the checkbox...it is cool. I mean that in the field itself allow the year. It should be enough to filter and is cleaner and takes less space.

It's acting like that already. :)

AH, IT WASN'T CLEAR WHEN I TRIED IT...THEN YOU CAN DEFINITELY MAKE THE COLUMN MORE NARROW FOR BOTH DATE FIELDS. PUT THE TIME ON SECOND LINE IN THE UPLOADED COLUMN.

JoshBone commented 5 years ago

Why did you combine the uploaded reports and submission under My Reports? I preferred it separate.

I thought that it looks a bit more organised, but define the menu how you would like to see, and that's how it's going to happen...

I like:

MY DATA

  • My Profile
  • My Agences
  • My Reports
  • Flags and Alerts

MENU

  • Submit Reports

    • Manual Submission
    • Upload CSV
  • Reference Data

    • Agencies
    • Reports
    • Institutions
    • Countries
  • Statistics
  • Documentation

FIXED

AGREE KM Add link to documentation, no? Deactivate all the non-active menu items (e.g. My Agencies).

JoshBone commented 5 years ago

I still don't like the field boundaries. It looks like you should enter something. Are you worried about the aesthetics if we get rid of the boundaries? Is there no way to make it look nice and also simply be "flat" data on a white background. (in the very least make the field background pure white.)

The thing is that the data is the same form-data. I think it looks much nicer that you can change the view when you edit, and you just have to enter the data into real fields... I can make all kinds of styles, lighter border, lighter text color, but still want to keep them as fields.

Well, then, make the background white and quite light or checked borders.

FIXED / I think it looks cool, like this

AGREE KM

Gyukat commented 5 years ago

I still don't like the field boundaries. It looks like you should enter something. Are you worried about the aesthetics if we get rid of the boundaries? Is there no way to make it look nice and also simply be "flat" data on a white background. (in the very least make the field background pure white.)

The thing is that the data is the same form-data. I think it looks much nicer that you can change the view when you edit, and you just have to enter the data into real fields... I can make all kinds of styles, lighter border, lighter text color, but still want to keep them as fields.

Well, then, make the background white and quite light or checked borders.

FIXED / I think it looks cool, like this

AGREE KM

YOU CAN USE THE SAME FORMAT FOR THE INSTITUTION VIEW PAGE. WE WON'T YET UPDATE, BUT LET'S MAKE THE "LOOK" THE SAME.

Gyukat commented 5 years ago

THINGS LEFT TO DO

TODAY: New Report / Edit

Gyukat commented 5 years ago

SIDE MENU:

MY REPORTS MENU

New Report/Edit Report

Documentation:

Gyukat commented 5 years ago

Report Submission Form

Report View Form

My Reports Menu

Reports Menu

Gyukat commented 5 years ago

Don't forget the list above!!!!

JoshBone commented 5 years ago

The two pop-up boxes (i.e. programmes and files) have both an "x" and a "close" button. We should decide which and be consistent.

What's the decision with this one?

Gyukat commented 5 years ago

FIXED The best solution would be to use grey "close" buttons at the bottom left corner of all the pop up boxes consistently in all cases (i.e. create and edit as well as view). Then for the View you just keep the button there.

If this is too hard and you have to choose, then just the "x" because it is already used on the create and edit...

JoshBone commented 5 years ago

Regarding to the previous one: Modals can be closed via 'Esc' button and also when you click outside the box. If I got rid of the 'X' button and have only the grey 'Close' should I get rid of these extra two behaviour as well?

Gyukat commented 5 years ago

I can't think of any particular problem if you keep the existing methods (all three). Am I missing something? Is there reason, we would need to click to update data or something?

Gyukat commented 5 years ago

Josh [9:54 AM] Hi @Colin and @Gyukat, Couple of things which I did in the last couple of days (which are ready to be tested on admin.test.deqar.eu):

  1. Users with ‘admin’ rights are able to edit the records in the reports menu as well. (The edit button is not displayed for regular users and obviously the endpoint won’t accept edit requests.) I have a question here. So django has a built in way to mark admin users. Those are the users who can log-in to DjangoSuit (who has is staff status) are considered as admin. I saw in DjangoSuit that several agencies have this option set. Is there any particular reason for this, or it was ad-hoc/accidental? If there is a reason, I can include Groups and we can create a separate Group entity for EQAR staff and run the checks against that group.
  2. When ‘Submit’ is pressed on the Edit Report form, the record won’t be send immediately, but an optional input field appears where you can add some detail about your updates.
  3. A) Minor change: I’ve switched InfoBox (flags and update log) and Submit / Close buttons and made the Info hidden in general. I thought it puts the managing buttons more in focus. Are you okay with this?
  4. B) Each update is now creating a separate log entry (ReportUpdateLog table) only when the update detail was filled. I thought that otherwise accidental saves would always add a new line, so the update log would be huuuge… We can still decide to do so, but then let’s just only display the latest 3 - 5 updates.
  5. C) Improvement for later - I wanted to use the same kind of popup for submission, but I had some shortage with the current form library we are using, namely with the current version, you can’t fire validation separately, only together with submission. The latest/newest version can do this trick, but for some reason it breaks the already functioning popup-form functionality. So it needs further investigation which I’d like to do later, not to be held up by this.
  6. Added the function ‘Request Deletion’. After a confirmation window a ‘high level’ flag (with the text: ’Deletion Requested.’) will be added to the report.
  7. A) Improvement for later - I’d like to hide the Request Deletion button once a record was already “deleted”. (Currently new requests aren’t really doing anything…)
  8. Added the function for ‘admin’ to be able to remove flags. This can be achieved in Edit mode only with the regular ‘x’ next to the flag. After confirmation the request for removing a flag is immediately sent to the endpoint, so there is no need to submit the report once again… What happens in the background is that in the flag table active will be set to ‘False’ and ‘removed_by_eqar’ will be set to True. This way we can avoid the flag to be triggered once again if flags are re-assigned automatically. An updateLog will be also created. Question: ‘Should I include the flag text to the update log?’ Let me know what you guys think any text that should be updated, etc... Institution Form is on the way I’m really hoping to roll out that one this week.

Colin [3:45 PM] Quick response re. 1) I think that was accidental, as agencies shouldn't log in to DjangoSuit. So in my view we can use the staff status to signal admin/full edit rights.

Gyukat [4:41 PM] Agree…1) accidental. 3a) don’t hide, but deactivate…so that people can see that it was already requested.

Gyukat commented 5 years ago

Josh [9:54 AM] Hi @colin and @Gyukat, Couple of things which I did in the last couple of days (which are ready to be tested on admin.test.deqar.eu):

1. Users with ‘admin’ rights are able to edit the records in the reports menu as well. (The edit button is not displayed for regular users and obviously the endpoint won’t accept edit requests.) I have a question here. So django has a built in way to mark admin users. Those are the users who can log-in to DjangoSuit (who has is staff status) are considered as admin. I saw in DjangoSuit that several agencies have this option set. Is there any particular reason for this, or it was ad-hoc/accidental? If there is a reason, I can include Groups and we can create a separate Group entity for EQAR staff and run the checks against that group.

SO, YES, THE EXISTING SETTING SHOULD BE FINE. WE NEED TO SIMPLY CHANGE THE MISTAKEN AGENCY STATUS.

2. When ‘Submit’ is pressed on the Edit Report form, the record won’t be send immediately, but an optional input field appears where you can add some detail about your updates.

THIS IS VERY NICELY DONE! I REALLY LIKE THE LOOK OF IT. AND VERY EASY FOR END USERS.

ONLY CRITIQUE IS THAT THE SUBMIT BUTTON TAKES YOU BACK TO THE EDIT RECORD. WHEN YOU SUBMIT AN EDITED RECORD, IT SHOULD TAKE YOU TO THE RECORD IN "VIEW MODE" SO YOU CAN SEE YOUR CHANGES AND ALSO HOW THEY ARE REFLECTED IN THE INFO.

3. A) Minor change: I’ve switched InfoBox (flags and update log) and Submit / Close buttons and made the Info hidden in general. I thought it puts the managing buttons more in focus. Are you okay with this?

THIS IS FINE AS LONG AS THE "CLOSE BUTTON" IS CONSISTENTLY ON THE LEFT SIDE THROUGHOUT THE SYSTEM.

4. B) Each update is now creating a separate log entry (ReportUpdateLog table) _only when the update detail was filled_. I thought that otherwise accidental saves would always add a new line, so the update log would be huuuge… We can still decide to do so, but then let’s just only display the latest 3 - 5 updates.

I THINK WE SHOULD INCLUDE ALL, SHOW 5 AND INCLUDE A "SEE MORE"...I HOPE THAT THERE WON'T BE TOO MANY CASES OF BLUNDERS. LET'S ASSUME THAT THE AVERAGE PERSON WON'T REALLY TOUCH THEIR RECORDS VERY OFTEN.

5. C) _Improvement for later_ - I wanted to use the same kind of popup for submission, but I had some shortage with the current form library we are using, namely with the current version, you can’t fire validation separately, only together with submission. The latest/newest version can do this trick, but for some reason it breaks the already functioning popup-form functionality. So it needs further investigation which I’d like to do later, not to be held up by this.

FINE. WE STILL HAVE THE PROBLEM THAT THERE IS AN ALERT WHEN PEOPLE USE THE UPLOAD FILE METHOD.

6. Added the function ‘Request Deletion’. After a confirmation window a ‘high level’ flag (with the text: ’Deletion Requested.’) will be added to the report.

THIS IS GREAT FOR END USERS. THE ADMIN SHOULD ACTUALLY HAVE A CORRESPONDING: "ACCEPT DELETION/DELETION" ...AND BOTH THIS BUTTON AND THE FLAG REMOVAL "BUTTON" SHOULD INCLUDE A POSSIBILITY TO PROVIDE A NOTE TO INFORM END USERS WHY THE REQUEST WAS ACCEPTED OR REJECTED. (PROBABLY SHOULD BE HOOKED TO AN ALERT AT SOME POINT...)

7. A) _Improvement for later_ - I’d like to hide the Request Deletion button once a record was already “deleted”. (Currently new requests aren’t really doing anything…)

YOU CAN DEACTIVATE THE BUTTON--PERHAPS INCLUDE A MOUSEOVER THAT DELETION HAS BEEN REQUESTED...I THINK THAT YOU MIGHT CONSIDER SOME MORE VISUAL SIGNAL THAT A RECORD HAS BEEN REQUESTED FOR DELETION...MAYBE IT COULD BECOME LIGHT RED AND LIST "UNDER CONSIDERATION FOR DELETION". RIGHT NOW, IT IS REALLY HARD TO TELL THAT SOMEONE HAS REQUESTED DELETION...YOU HAVE TO OPEN UP THE INFO.

8. Added the function for ‘admin’ to be able to remove flags. This can be achieved in Edit mode only with the regular ‘x’ next to the flag. After confirmation the request for removing a flag is immediately sent to the endpoint, so there is no need to submit the report once again… What happens in the background is that in the flag table active will be set to ‘False’ and ‘removed_by_eqar’ will be set to True. This way we can avoid the flag to be triggered once again if flags are re-assigned automatically. An update Log will be also created. Question: ‘Should I include the flag text to the update log?’
   Let me know what you guys think any text that should be updated, etc...
   Institution Form is on the way I’m really hoping to roll out that one this week.

YES, THIS LOOKS NICE. AS I MENTIONED ABOVE, IT SHOULD INCLUDE AN OPTION TO PROVIDE A NOTE. I THINK THE REMOVED FLAG TEXT CAN BE ON THE LOG AS WELL AS ANY NOTE PROVIDED...AM I MISSING SOMETHING?

I HAVEN'T NOTICED ANY PARTICULAR PROBLEMS WITH TEXT...BUT I WILL KEEP LOOKING.

Colin [3:45 PM] Quick response re. 1) I think that was accidental, as agencies shouldn't log in to DjangoSuit. So in my view we can use the staff status to signal admin/full edit rights.

Gyukat [4:41 PM] Agree…1) accidental. 3a) don’t hide, but deactivate…so that people can see that it was already requested.

Gyukat commented 5 years ago

BTW, I TRIED TO UPDATE A RECORD BY ADDING A URL. IT SEEMED TO ACCEPT BUT THE DATA DID NOT SHOW UP.

Gyukat commented 5 years ago

JOSH, I KNOW YOU ARE GOING TO HATE ME FOR THIS...BUT CAN'T THE ADMIN USERS HAVE ANOTHER SECTION OF THE MENU TO MANAGE FLAGGED RECORDS. YOU CAN DO THIS IN LATE JULY...AFTER OTHER PARTS ARE FINISHED.

THIS WOULD MEAN THAT THERE WOULD BE A REPORT LIST AND INSTITUTION LIST AND THESE WOULD HAVE ONLY FLAGGED RECORDS. THE MENU FIELDS COULD BE ADJUSTED TO FIT THE TASK OF MANAGING FLAGS. WHEN WAS FLAG ADDED, BY WHOM, FLAG LEVEL/FLAG TYPE/COMMENT. I THINK/HOPE IT WOULD BE EASY AS YOU COULD JUST USE THE SAME BEAUTIFUL MENU STRUCTURE THAT YOU HAVE MADE (THIS IS ME ATTEMPTING TO BUTTER YOU UP!).

Gyukat commented 5 years ago

What happens when a bad link is provided?

Look at this: http://www.pka.edu.pl/raporty/2014/11/14/2014._UMed_WWL_oc._inst.pdf

Screen Shot 2019-08-19 at 20 38 39

It is the second "institutional evaluation" on this page...https://www.eqar.eu/qa-results/search/institution/?id=1970

dead link.

Gyukat commented 4 years ago

no…it is fine

On 2019. Mar 27., at 20:56, Josh notifications@github.com wrote:

Regarding to the previous one: Modals can be closed via 'Esc' button and also when you click outside the box. If I got rid of the 'X' button and have only the grey 'Close' should I get rid of these extra two behaviour as well?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/EQAR/deqar_frontend/issues/3#issuecomment-477323619, or mute the thread https://github.com/notifications/unsubscribe-auth/AfjUe6ybtaTB4ICd99hFpDJOk7RL8xR7ks5va8zQgaJpZM4bXlDv.