Ensure that the modification and creation time for publications make sense.

ES-DOC / esdoc-questionnaire

ES-DOC Questionnaire (webform generator for creating CIM Documents). POC: @allynt

Other

2 stars 1 forks source link

Ensure that the modification and creation time for publications make sense. #434

Closed allynt closed 8 years ago

allynt commented 8 years ago

WHO: @murphysj

Ensure that the modification and creation time for publications make sense. Sylvia has noted the following issues:

The "Publication Date" in the ATOM feed does not correspond to the modification date of the publication object in the db (nor the explicit creation date in the XML content itself).
- (I know this b/c a script ran which supposedly changed and then saved the publications, but the date that that script ran does not appear.)
- Also, the template controlling the publication date in the feed should be getting that information from the "modified" field but it looks like it is coming from the "created" field.

allynt commented 8 years ago

Does it make sense to explicitly include both the creation date and the modification date in the feed templates?
- No, b/c a different modification date is only a side-effect of an edge case (republishing)
Does it make sense to include all of this information as comments w/in the XML content?
FYI: The date in the comment section of the XML content is the date that the XML was created (or recreated)
FYI: The "createDate" element in the XML content is the date that the model (not the publication) was created.

allynt commented 8 years ago

So...

in the feed, "publication date" should be set to the time that the XML content was created (this should match the "modified" field, but I need to double-check)

allynt commented 8 years ago

Discovered that the "modified" field was not changing at all in any of the models it was being used in! Added Django's built-in "auto_now" kwarg to fix this.

allynt commented 8 years ago

Demonstrated to Sylvia on 15 January 2016.