search

nikobojs / manuscrape_electron

ManuScrape desktop app for Windows 11
5 stars 2 forks source link

Keep export-log #71

Open Pedrotheplant opened 5 months ago

Pedrotheplant commented 5 months ago

It would be nice to have an export log, so one can see when the last time one exported the observations, thus avoiding dublettes.

nikobojs commented 5 months ago

There is also a feature request (https://github.com/nikobojs/manuscrape_electron/issues/66) that includes a variety of ways to export using date ranges.

If we combine this with information about "when who exported what", it should solve the confusion i think. Interesting proposal !

samuelhimmelstrup commented 4 months ago

I will look into this. Not sure if I can assign myself to this issue, maybe it is only @nikobojs who has permission to assign?

samuelhimmelstrup commented 2 months ago

Okay @Pedrotheplant, I need a bit of additional info before I can do this:

1) Do you need to see all exports that have been made by all contributors for a project, or just your own exports? 2) With new options for exporting, how much info do you need to see?

It would be very nice if you could show me the view you have in mind. Like for example:

Exports: Team Member B: All observations before 17/02/2024 You: From: 03/07/2023 To: 22/01/2024 You: Cherrypicked (With option to click for more info)

or only your own and with date ranges for the "All observations" option:

Your Exports:

Many ways to do it, so I would appreciate some more feedback on what would be the most useful :-) Cheers Samuel

Pedrotheplant commented 2 months ago

Hi Samuel! Awesome that you're looking into it!

1: I think the project owner needs to be able to see all exports by all contributors. Once the feature of letting other contributors export (#87), we could perhaps add a conditioned drop down, saying "let contributor access export logs of: their own exports only <--> all project members' exports", if the contributor is allowed to export.

manuscrape export

2: It would be nice to see whatever is needed to replicate the export. So basically the export date, the user and the export parameters. So:

Export log

Does it make sense? :)

samuelhimmelstrup commented 2 months ago

1) alright, project owner can see everybody exports. What about other members, can they see everybodys exports or just their own?

2) just to be sure, can you specify what is meant by "attributes". The cherry picked option is the most complicated to implement, so I want to be sure what is needed. Is it "check off any number and combination of observations" or "all observations (in date range) that has a special characteristic. Hope my question makes sense 🙂

Pedrotheplant commented 2 months ago

  1. Can we make that a toggle for the other members? So as a default they can only see their own exports, and then "see all exports" can be toggled?

  2. I'm not entirely sure how to read your examples, so let me know if my answer doesn't make sense :) If I read @nikobojs suggestion in #66 correctly, then it's the first of your two examples :)

I had forgotten about his suggestion in #66 , when I wrote the previous comment, my apologies! I think the parameterbased one (your second example) is probably best left for subsequent data analysis outside of manuscrape :)