Metadata
- Source
- SJRK-345
- Type
- New Feature
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- N/A
- Reporter
- Gregor Moss
- Created
2020-04-22T13:39:39.840-0400 - Updated
2020-11-26T11:12:26.455-0500 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Storytelling Tool Server
Description
Once server-side autosave has been implemented (SJRK-289), there should be a task created to automatically clear out any unpublished stories that are older than a certain amount of time.
Consideration should be given to how old a story is before it is determined to be "too old", as we don't want to accidentally delete something that an author has been chipping away at. Since the SJRK-289 work will be adding timestamp values for first created date and last modified date, we'll have to decide which to use to calculate this duration.
Design questions:
- How old should a story be before it is determined to be "stale"?
- What timestamp should we use to determine staleness? Last modified? Created?
- What should happen to localStorage copies of stale stories that have been cleared out?
Comments
-
Gregor Moss commented
2020-10-28T01:50:35.045-0400 the story grade's model value "timestampLastModified" was removed from the SJRK-289 development branch at commit df267d73e9007b78a18075d99bf6c0d12a409bf9. This should be reused when the work for this Jira is picked up.
-
Gregor Moss commented
2020-10-30T01:14:41.568-0400 The change in "tests/ui/js/ui-storyUiTests.js" at commit d8de999f320e05ac82102c448a36f8573436b5fd is also necessary for the tests to pass with this update.