Sorry to interrupt the conversation, supporting Ken's 3rd option, to check the integrity of the file we can use hashes to confirm that the data has not been edited. But the hash needs to be checked twice, before upload and after upload and match the value accordingly. Just a thought, open to suggestions. Regards, Afifa On Wed, 7 Jul 2021, 14:43 Andrew McConachie, <andrew.mcconachie@icann.org> wrote:
On 6 Jul 2021, at 17:51, Ken Renard <kdrenard2@gmail.com> wrote:
3. User runs the tool and output is generated. Users are then asked (and encouraged) to take an independent action to publish the data (such as run a publish_data.sh script). The user may review the data before executing the action to publish.
Hi Ken,
This one is tricky from a quality control standpoint.
First, because it requires that the tool store data locally somewhere, and then be able to retrieve it later. This can break for a number of reasons.
Second, it gives the user a chance to edit the file before it is sent. With this choice we’re going to end up with lots of user edited data entries, or failed data push events where the user tries to edit the data and then breaks the format of it. Thereby breaking the whole process.
--Andrew _______________________________________________ rssac-caucus mailing list rssac-caucus@icann.org https://mm.icann.org/mailman/listinfo/rssac-caucus
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.