Skip to content
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

UX Proposal: Editor Media Gallery Date Filters #25583

Closed
jakejones1984 opened this issue Jun 19, 2018 · 4 comments
Closed

UX Proposal: Editor Media Gallery Date Filters #25583

jakejones1984 opened this issue Jun 19, 2018 · 4 comments

Comments

@jakejones1984
Copy link
Contributor

jakejones1984 commented Jun 19, 2018

date_filters_u

Users have reported that it's important to be able to display a specific date range of photos when they are shown in the Editor's Google Photos Media modal dialog.

This is essential for a few reasons

  1. Currently the only way to reach older photos is to scroll down and trigger the next set of photos to load. As these only load in batches of 20, if you have a large Google Photos set then this takes a long time and is very frustrating.
  2. Picasa places are hard limit on the number of photos that can be requested (1000 as reported by @johngodley). This means some users are unable to access their old photos even when they persist with the scrolling approach described above.
  3. If you're anything like me, you don't organise your Google Photos but you do know roughly when a given photo may have been taken. As a result the ability to filter by a given range of dates is very useful when trying to locate a photo.

Potential Solution

A potential solution to this is adding a date filtering UI (see above for prototype of this) to the modal. This would allow a user to set a start and end date to load only photos within those dates.

Doing this requires:

  1. Upgrading the Picasa integration to include date filtering using the published-min and published-max fields and then upgrading the WPCOM API to allow these filters to be called (note: this still requires investigation to see whether Picasa will actually respect these query parameters).

  2. Addition of new UI. It would be good to get some input from Design here to validate and improve the approach above.

@jakejones1984 jakejones1984 added [Feature] Post/Page Editor The editor for editing posts and pages. [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR Design [Type] Enhancement labels Jun 19, 2018
@jakejones1984
Copy link
Contributor Author

Update

Picasa API no longer supports published-min published-max fields. Therefore to implement this functionality we will need to upgrade the entire integration to use the Google Photos API. This is being discussed internally.

@davewhitley
Copy link
Contributor

davewhitley commented Jun 19, 2018

The UI shown here looks like to me. I would like to see the date range filter integrated into the search bar.

screen shot 2018-06-19 at 4 08 19 pm
screen shot 2018-06-19 at 4 08 01 pm

@davewhitley davewhitley removed the [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR label Jun 19, 2018
@jakejones1984
Copy link
Contributor Author

@drw158 Thanks very much for your feedback. Very much appreciated.

For technical reasons the search might be disappearing in the near future. That is why I haven't explored the approach you've outlined.

In addition, I feel the date filtering is probably one of the most important ways to interact with Google Photos (other than filter by Album) and so I was trying to avoid it getting "lost" within the rest of the UI.

This is being discussed internally on teamtinker P2.

@stale
Copy link

stale bot commented Mar 17, 2019

This issue has been marked as stale and will be closed in seven days. This happened because:

  • It has been inactive in the past 9 months.
  • It isn't a project or a milestone, and hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, `[Status] Keep Open`, or `OSS Citizen`.

You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants