Ticket #872 (new Issue)

Opened 4 years ago

Last modified 4 years ago

versioning documents when submitting to CMIP5

Reported by: rupert Owned by: bryan
Priority: blocker Milestone: V1.2 Questionnaire release
Component: WP6 - CMIP5 Questionnaire Version:
Keywords: subCMIP5 Cc: charlotte, gerry
Requirement: http://metaforclimate.eu/Work-Package-2/Developing-the-CIM/Project-Requirements-summary.htm

Description (last modified by rupert) (diff)

When a plaftform document is re-submitted to CMIP5 due to it being edited, the version number does not change, although the persisted xml document is not overwritten as the new one has an additional "_" compared with the last. Further, the related feed gets a new entry but this entry is identical to the previous one. After my email about this Bryan has suggested that this does not sound correct.

Here are the emails:

Hi Bryan/Gerry, 
 
When is the version of a document meant to change? I've just played with  the latest version of the CIM (after enabling the submit to CMIP5  button)  and the platform document version does not appear to increment. 
 
So, for example ... 
 
1: Create a valid platform 
2: submit to CMIP5 
3: edit the platform details and save. 
4: submit to CMIP5. 
 
In both submissions the ID and version of instance is the same but the  persisted document gets an additional "_" added to it so we don't lose  the previous version. This continues with another save and submit cycle  (i.e the latest one gets two "_"'s). So we appear to be persisting  updated documents by adding an underscore to the file name. 
 
Is that what you expect? If so, when does the version change? 
 
I've looked at the relevant feed and we get exactly the same feed  information replicated each time we submit. Is that what is expected?  How does the software reading the feed know about using "_" for updated  versions? 
 
Thanks for the clarification 
 
-- Rupert
This sounds wrong!

(I wont be able to think more about it for at least a week)

B

Hi Bryan,

OK, I'll ticket you :-). 
 
Beware, this is my opening question about versions. There may be some  other problems (related to our conversation yesterday) depending on how  it all works. 
 
Cheers 
 
-- Rupert

For information, the additional problems I am talking about in the above email are:

1: if we increment version numbers for documents and have separate submit to CMIP5 buttons then we will (might?) end up referencing the wrong version.

2: What gets incremented when we submit a model document as this consists of lots of documents in a hierarchy. Do they all get incremented? What happens when we only update one component and resubmit. Do all components get their version incremented?

Change History

comment:1 Changed 4 years ago by rupert

  • Description modified (diff)

For info here are two entries in the feed that were generated. Note there is no version information in the feed. Also note, if we are going to use timestamps to know which is the latest version then we should be using datetime as people may submit more than once in a day.

    <entry>

        <id>urn:uuid:33b24760-dc3c-11df-90e7-00188bd7eb83</id>
        <title>minimalplatform ()</title>
        <updated>2010-10-22T00:00:00Z</updated>
        <published>2010-10-20T00:00:00Z</published>
        <link href="/cmip5/platform/33b24760-dc3c-11df-90e7-00188bd7eb83/1/" type="application/xml"
            rel="via"/>
        <summary>platform:minimalplatform ()</summary>
        <content src="/cmip5/platform/33b24760-dc3c-11df-90e7-00188bd7eb83/1/"
            type="application/xml"/>
    </entry>
    <entry>
        <id>urn:uuid:33b24760-dc3c-11df-90e7-00188bd7eb83</id>
        <title>minimalplatform ()</title>
        <updated>2010-10-22T00:00:00Z</updated>
        <published>2010-10-20T00:00:00Z</published>
        <link href="/cmip5/platform/33b24760-dc3c-11df-90e7-00188bd7eb83/1/" type="application/xml"
            rel="via"/>
        <summary>platform:minimalplatform ()</summary>
        <content src="/cmip5/platform/33b24760-dc3c-11df-90e7-00188bd7eb83/1/"
            type="application/xml"/>
    </entry>

comment:2 Changed 4 years ago by charlotte

  • Type changed from Task to Issue

Changed the type to "Issue" as a way of identifying tickets that require thinking and a decision.

comment:3 Changed 4 years ago by charlotte

I asked Sarah to put Versioning Issues on the agenda for the year 3 meeting.  She has put it in the afternoon of day 1 with our discussion about cmip5 metadata.  We can move it if necessary.  

Year 3 agenda:  http://metaforclimate.eu/trac/wiki/ticket/11

Note: See TracTickets for help on using tickets.