-
Notifications
You must be signed in to change notification settings - Fork 6
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
updated article editor & article views #53
Comments
@eplebel The editor mockup only has one 'Protected access' checkbox for the study materials and data URLs (rather than one checkbox per URL), should this be set for all URLs together i.e. if one URL is protected then they all are? |
correct and this limitation applies to the updated view as well whereby the "protected access; login required" text will appear to the right of each URL (even if it only applies to one of them) |
@eplebel I just pushed the bulk of the changes to staging. There are still a few outstanding issues (e.g. the popups for the reporting standards and the transparency badges, the input adornments) but most of the work for the editor screen itself should be done. Let me know what you think. I had to upgrade a few libraries (react, material-ui and some related things) to get all the the outlined inputs working correctly so there were a few changes that had to be made to the code to account for this. Everything else should be working as it was before but if you come across anything strange, let me know. |
awesome! overall things are looking good. i'm going to make a list of the major stuff still missing (or still not working, e.g. DOI LOOKUP doesn't appear to be working) pronto! also, could you add the search results page functionality, as mentioned in this comment, thanks!: |
here's the list (with new or pre-existing mockups moved here to avoid ambiguities/save us time!):
hopefully we can have prompt iterations for these given we're a bit behind schedule and was really hoping to be able to show contract#1 features to the team here in Leuven by begining of academic term in a few weeks, thanks! |
@eplebel Thanks for all of that, it clarified a lot. I was trying to sort out as many of the issues as possible yesterday because I won't be able to get back to this until next Wednesday. There are still a few left (and a few fixes to my fixes 😄) but hopefully they won't take too long. And I haven't forgotten about the search box changes either, they're on the way! |
ok thanks for heads up. i will carefully review/test all contract#1 pages/features, and then make a list of all outstanding issues so that we can iterate as efficiently/promptly as possible upon your return! |
final outstanding minor issues (above & beyond what's mentioned above):
|
great work on latest batch of commits, it's really coming together! (20945ec...e444964 and e444964...8608708). everything is working as expected. only the following 3 minor issues were identified:
after these are addressed, we're basically almost there. i'd say next critical items are as follows (we could potentially punt on the remaining minor issues):
|
@eplebel I've pushed a bit of a fix for the issue with expanding the text in the popup. It's still not correct though because if a there's a lot of expanded text the position of the popup is likely to move a lot to fit it all in. One possible solution is to have the popups appear only when the badge is clicked and disappear when the user clicks away. That's not ideal though, I know. Just wanted to let you know the story with it. |
ok, if you can address the overflowing chips issue, i think we can call this contract done! once that's done, we could then push everything to the master branch, but perhaps we can try to coordinate a rough time, so i can be at the ready in case anything goes wrong (given lots of major changes are going through??)... thanks again @mickaobrien for all your solid work on this! |
Great! I had a look at the overflowing chips the other day and it was trickier than I expected, but I should be able to sort something out later today hopefully. I'll push it to staging for you to have a look and once you're happy with that we can push to master, maybe early tomorrow if that suited you? |
sounds good re: overflowing chips, and re: pushing to master tomorrow morning! |
Just pushed a fix for the overflowing chips to staging. Let me know what you think. |
summary of improvements/changes to the article editor:
(new fields - and some of the other new features - will require updating the data model (see updated ER diagram (entities to-be-added in blue))
DETAILS:
(Article type dropdown default remains "Original")
Reporting standards dropdown defaults to "Basic 4/Basic 7 (retroactive)" (as in mockup above) and should use the proper Material UI Outlined Select text field with "Reporting standards" as label.
details for the "Basic 4/Basic 7 (retroactive)" component:
for the various other reporting standards, display the following:
(For the remaining reporting standards, badge popups are displayed the same as the MARS (2018) popup except with different reporting standards name, description text, & hyperlink of course)
for both "Edit" or "New" article actions, editor will be loaded in an improved modal window:
Article views (live demo) for the different article types (in order):
The text was updated successfully, but these errors were encountered: