Provenance records are written out even if no provenance info is set in the tool

Description

To reproduce:

  • Make sure you don't have a ~/.ocelot/provenance.properties file. (If you have one, move it somewhere else.)

  • Open Ocelot. Open File > Profile to verify that you have no values set for any of the provenance categories.

  • Open any XLIFF file.

  • Make any change that triggers the addition of a provenance record (add a flag, modify an existing flag, etc).

  • Save (or save as) the file.

If you look at the file that was saved, you'll see that Ocelot saved a useless provenance record that contains no information, eg:

This isn't great behavior, because it generates useless data. One alternative would be to just not write provenance in this situation. If we choose to go that route, we shouldn't do it silently - the user should at least be alerted to the fact that they're making changes without provenance.

A more intrusive (but possibly better) behavior would be for the app to check if provenance info is defined (at least 1 field) at startup, and if it's not, prompt the user to enter some. This will also guide new users to do the right thing.

Environment

None

Assignee

Chase Tingley

Reporter

Chase Tingley

Labels

None

Components

Fix versions

Priority

Major
Configure