DDMAL / CantusDB

A new site for Cantus Database running under Django.
https://cantusdatabase.org
MIT License
5 stars 6 forks source link

Source List page: Filtering by Century could be improved #991

Open jacobdgm opened 1 year ago

jacobdgm commented 1 year ago

I just got an email from Debra:

A suggestion has come in that I think will improve the use of the pull-down list for century for CantusDB sources.

I'm on this page: https://cantusdatabase.org/sources/?segment=4063

Would it be possible to have "Century" just as: "9th century", "10th century", etc. up to "17th century" in the pull-down list, and then have 2 additional fields with this for one: "1st half", "2nd half", and then this for the next: "1st quarter", "2nd quarter​‌", "3rd quarter," "4th quarter." (no year dates are needed, then)

The pull-down lists will be shorter and easier to manage (see screenshot).

I know this changes the search programming, which you currently have matching all of the same century (I think) no matter which part of the century is selected. (So, this is already great, that it pulls up all sources of the same century even if some have a more detailed specification.)

Does this make it more streamlined or more difficult on the back end? For me, I can see it being more streamlined for the user, because I can specify the century if I know it, and then if I know which half I can choose that, and if I know even more I can continue to the quarter and specify that (or I can leave it blank at whatever point I am unsure). But, if it splits up the data too much and you can't attach "1st half" because it's not 'century-specific' then I understand the difficulty. In my description, above, "1st half" would be in a separate pull-down and would be applied whenever the user wanted that, based on their selection of the "century" field - but there wouldn't be a different "1st half" option for each century --- instead, just one that would rely on the previous field for context. If you know what I mean.

Also, there is a 9th and a 09th in the current list that should be cleaned up, regardless of what happens to this Century field(s).

This would be a nice thing to implement, and I can see how it would improve user experience.

This entails two main tasks:

We have options for the second of these points. I'll create a comment below this one and start recording some of the thoughts I have.

jacobdgm commented 1 year ago

For the Century model: