08.08.2022 TT Agenda - QualitativeDataRepository/TechnicalTeam GitHub Wiki

Admin:

• Welcome back SK

Seba:

• Did you get connected to SYR IT about remote access?
• If so can you verify the new Prod is synching backups at SYR?

Jim

• Report https://github.com/QualitativeDataRepository/TechnicalTeam/wiki/8-8-2022-Tech-Team-Report
• Major discussion point is next steps on QDAS previewer
• Storj

Things on back burner, but to remember:

• Should we revisit using Sentry
• Seba to increase verbosity of logging when we get a page / escalation (so we can more easily diagnose problems)
• JM - auto-vacuuming the guestbook for cleaner metrics

Notes

• No movement on storj or guestbook (but not pressing)
• Seba - still trying to get access, will

QDAS discussion:

• Zipping done by JS - some range of queries in JS weren't being supported by DV so it took a bit longer. In general - all things JM knows how to explore are working well. The Scitoscape viewer is working...
• Looking for additional test files
• Potential for editing
• ODP at Harvard - page restricted + auxiliary files accessible
• • Edit without editing the original version
• Open question - What extent will people want to have original file(s)
• • Aux file might be most interesting for co-author
• • The biggest challenge is going to be cleaning up files for release
• Restricted vs Unrestricted - in DV we have only two levels. Maybe work around is the restricted file with permission levels differed ... (No :) because it always has the parent file's permissions)
• We could push back to a second file - and keep original - dealing with access restrictions differently
• There is nothing in DV to "hide" a file ... (Hidden old version)
• Trigger a publish hook so that the original version gets deleted at publication (?) -

Possible workflow (for a pre-publication hook) [Incomplete]:

• • Click QDAS editor
• • This creates new file (which is an editable version)

External tool

• There is nothing that stops external apps from deleting the file they are working on
• Pushback edited and delete original...

Prototype is on dev

• SK to review and offer feedback on interface
• Next steps - editing a file
• Use cases (in terms of editing QDAS projects)
• • Delete codes (which turns these into orphans)
• • Delete a single file
• • Delete all files associated with a particular code
• • Delete Excerpts associated with a particular file or code