Marking as watch later shouldn't delete historical WatchAction data

[josephguillaume]

This is more of a long term comment regarding the data model used.

If a movie has watch actions registered, selecting "watch later" deletes that data.
This means that information about when the movie was previously watched gets deleted.

It seems it would be more appropriate to instead add data indicating that the user wishes to watch it again.

One option would be to create a new watch action with
schema:actionStatus schema:PotentialActionStatus
If this option was used, it would make sense to consider whether to also use ActiveActionStatus, CompletedActionStatus, and/or FailedActionStatus.
Marking as watched would probably involve a WatchAction with CompletedActionStatus.

As a side issue, it appears that dc:createdAt, schema:startTime and schema:endTime currently all get set, and to the same time.
It would make sense to only set createdAt by default, and ensure that if data is set for start time and end time, it actually does refer to valid information about the start and end time of the user's watch action.

[NoelDeMartin]

Hey, thanks again for reporting an issue :D.

This behavior is something I implemented on purpose, given that with the current conceptual model a movie can only be "watched" or "pending". However, I have come across this use case myself and it is frustrating, so I was thinking on implementing the ability to rewatch movies (and also keep track of how many times you've watched a movie). I hadn't thought about it too much, but I like your proposal of using the actionStatus, so I'll keep it in mind.

About the timestamps, since the WatchAction was only created or destroyed, I was just setting the same date to all. But if I start creating actions before watching the movie, and use the actionStatus, I'll have to think about those. Thanks for the heads up.