pyDataverse
pyDataverse copied to clipboard
Add history functionality to pyDataverse objects
Purpose
- Add audit trail / history function to pyDataverse objects and function calls
Functionality
- Question: use file(s) to store information: CSV, JSON, ???
- #51
- Integrate with logging #44
- Integrate with OAISTree (#5 )
- Store history.json files outside oaistree structure (to seperate the two features)
- Re-do all steps: a dataset could even be created at another instance again, so all workflow steps which should be stored in the history can be done n-times.
- use state of pyDataverse object history to control workflow: OAISTree, API calls,
- save Dataverse id and alias after creation
- save Dataset id, title and internal id after creation
- save Datafile id, filename and internal id after upload
- synchronize pyDataverse object history with output (JSON, CSV, whatever)
- save username and base_url to API calls
- Filename:
history_ID.json - create one entry for each event/activity
history.json structure (DRAFT):
metadatadate-created: string, YYYY-MM-DD HH:MM:SShistory_version: version des history schemas
history: [{}]dataset_id: stringdataverse_dataset_version: stringdatafiles: [FILENAMES], ohne Pfadtimestamp: string, YYYY-MM-DD HH:MM:SSdescription: stringobject_type: dataset oder datafileobject_idcreatorchange_type: {dataverse_release: ,dataverse_process: }dataverse: init, update, delete, moverelease: init, update, delete, moveedit: major/minor release version change in Dataversedelete: major/minor release version change in Dataverse
internalspecific_change_type: nähere Beschreibung des change types, zbaussda
As discussed during the 2024-02-14 meeting of the pyDataverse working group, we are closing old milestones in favor of a new project board at https://github.com/orgs/gdcc/projects/1 and removing issues (like this one) from those old milestones. Please feel free to join the working group! You can find us at https://py.gdcc.io and https://dataverse.zulipchat.com/#narrow/stream/377090-python