In our meeting about revision dashboards, Sheppy mentioned that it would be great to have something like a revision "inbox" -- a list of all revisions made to the docs, with some marked as "read" and others marked as "unread".
See this mockup as an example:
This would require us to keep track of a "read" list for each user on the site. How difficult would this be to implement?
Do we really need a full-on "read" list? Or would a single pointer to last-read work as well?
The problem with a per-user/per-revision "read" list is that we'd have to keep a lot of records around, indefinitely. (ie. #-of-dashboard-users x #-of-revisions = a lot of data over time, depending on how we store the flags)
Maybe we could even use localStorage to track last-read and/or individual "read" flags on the client-side. There could be logic which occasionally cleans up "read" flags when the items in question haven't been seen in awhile.
This is the most comprehensive approach. The first one we're taking is a single pointer to a last-read date/time or revision #.
Yes, simply recording for each user the date/time of the last revision they checked out would be good enough... especially once we have that "review dashboard" that groovecoder and I discussed a few days back and I filed a bug on.
I agree, I for one don't really need an "inbox". I would love to flag a revision as my bookmark, so I can continue to read through the list starting with that point next time.
Ideally the dashboard view scrolls to that point automatically.
Not sure if that bookmark itself should be set automatically. I think it would be nice if I can flag the bookmark revision manually on my own.
I'm wondering how this plays together with filters. I want to go through all "en-US" revisions but also all "de" revisions and maybe other filter rules once we implement them.
Do we want to allow two or more bookmarks then?
Should we add an option to save your own filter rules and each can have a bookmark then?
Or do I think too complex? Do others have a use case for this?
Renaming this bug, since it's really now about bookmarking where you left off, not having "read" versus "unread" revisions.
I am wont fixing this bug as the revamped revision dashboard makes it a lot easier to keep track of the revision where you left off. By using the date picker there now, you can easily keep track of a chosen time frame as well.
Bookmarking documents is a completely different bug then (which we have filed as well I think).