Deal with the dynamic of the verification of capture.

[dadiorchen]

Currently, the workflow of generating capture data to CKAN is: the 1st day of every month, generate the capture data of last month, as @nmcharlton mentioned in the meeting, because now in the table we output the verification status, how do we deal with the changing of it, and the token minting too, because that we can not predict when do operator verify new coming captures.

We were talking about some solutions:

• Give some delay for the generation, like, generate the data two weeks later from the beginning of the month.
• Do not output the status of the verification.

What do you think @ZavenArra

[nmcharlton]

A third option:

• Monitor audit logs and periodically regenerate reports for any historic reporting periods for which events have been recorded

This raises questions about exactly what we're trying to report. Should it be more focussed on events (new captures, verifications, tokens minted etc.) during the given period, rather than states?

[dadiorchen]

zaven - VP Eng:pick: 6 days ago
Yeah, well I was thinking that to start off we should actually export ALL of an organizations captures each month, to capture the state at the data at the end of the month. Otherwise the organization cannot get a full set of their data that is up to date with verification status or other changes. Each time we run the export, we can split it into multiple files to make it managable.

zaven - VP Eng:pick: 6 days ago
Our capture data currently does not exist in a form that is truly 'final', so really the only option is to do a complete export each month for organizations that want this kind of access to their data.