Feature #176
Mis à jour par Matthieu Decorde il y a presque 6 ans
A description should be associated to every object of the Corpus view.
One part of this description would be automatically generated : function and parameters used for the creation of the object, creation date, TXM version used...)
Another part would be a free commentary.
h3. solution First proposals
* -add add a member TXMResult.userComment and save it in TXMResult.autoSaveParametersFromAnnotations() as for TXMResult.userName- see #2644 TXMResult.userName
** maybe better => shared the "description" field/member or Corpus object
* -add add a member TXMResult.txmVersion and save it in TXMResult.autoSaveParametersFromAnnotations()- see #2645 TXMResult.autoSaveParametersFromAnnotations()
* -creation creation date can be retrieve from the TXMResult UUID but it would be simpler to store it as is, eg. member TXMResult.creationDate and preference name creation_date- see TXMResult.creationDate and TXMResult.updateDate
finally see last evolutions of the Properties command creation_date
One part of this description would be automatically generated : function and parameters used for the creation of the object, creation date, TXM version used...)
Another part would be a free commentary.
h3. solution First proposals
* -add add a member TXMResult.userComment and save it in TXMResult.autoSaveParametersFromAnnotations() as for TXMResult.userName- see #2644 TXMResult.userName
** maybe better => shared the "description" field/member or Corpus object
* -add add a member TXMResult.txmVersion and save it in TXMResult.autoSaveParametersFromAnnotations()- see #2645 TXMResult.autoSaveParametersFromAnnotations()
* -creation creation date can be retrieve from the TXMResult UUID but it would be simpler to store it as is, eg. member TXMResult.creationDate and preference name creation_date- see TXMResult.creationDate and TXMResult.updateDate
finally see last evolutions of the Properties command creation_date