What's your idea?
- Currently the app fetches the full release date data from the metadata providers, and discards the day/month. Seems just published year is stored, displayed in book details page and exposed as a way to stort in UI.
- I propose we store full release date for the book to be available to sort and use in smart scopes.
What problem does it solve?
- Bookorbit does not store full release date.
- This means that if I create a Smart scope to display Recent releases, only sort option that is viable for my purpose is published year
- When I set books to be sored in published year, books are displayed in a random order.
This is a small, nitpicky change but would make the app feel more refined.
Anything else? (optional)
Implementation idea:
- Keep current
publishedYear as is.
- Add a
releaseDate field and store full release date as a separate entity. This data is already fetched from metadata sources from a cursory glance, we just change it to be stored as a proper date, and wire it up to be used in sorting.
- Add safeguards to write 01-01-YYYY if metadata source only supports year.
Want to help?
Yes, I'd like to implement this
Before submitting
What's your idea?
What problem does it solve?
This is a small, nitpicky change but would make the app feel more refined.
Anything else? (optional)
Implementation idea:
publishedYearas is.releaseDatefield and store full release date as a separate entity. This data is already fetched from metadata sources from a cursory glance, we just change it to be stored as a proper date, and wire it up to be used in sorting.Want to help?
Yes, I'd like to implement this
Before submitting