Discuss Data issueshttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues2024-02-12T15:27:32Zhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/486Install django-ninja as API2024-02-12T15:27:32ZFelix HerrmannInstall django-ninja as APIhttps://django-ninja.dev/#installation
- [ ] add django-ninja to requirements.txt
- [ ] add NinjaAPI to urls.py
- [ ] write health check test for ninjahttps://django-ninja.dev/#installation
- [ ] add django-ninja to requirements.txt
- [ ] add NinjaAPI to urls.py
- [ ] write health check test for ninjaDD2Felix HerrmannFelix Herrmannhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/485fix: update imprint2024-01-29T08:03:36ZStefan Hynekstefan.hynek@uni-goettingen.defix: update imprint> Die Niedersächsische Staats- und Universitätsbibliothek Göttingen (SUB Göttingen) wird vertreten durch die stellvertretende Direktorin Kathrin Brannemann.> Die Niedersächsische Staats- und Universitätsbibliothek Göttingen (SUB Göttingen) wird vertreten durch die stellvertretende Direktorin Kathrin Brannemann.Stefan Hynekstefan.hynek@uni-goettingen.deStefan Hynekstefan.hynek@uni-goettingen.dehttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/484request comment when dowload2024-01-12T10:07:35ZEduard Kleinrequest comment when dowloadHeikos wish:
when a user downloads a data set, it would be good to have a small pop-up window with the request to write a comment on this dataset to generate more communication on the platform (like: "Thank you for downloading and using...Heikos wish:
when a user downloads a data set, it would be good to have a small pop-up window with the request to write a comment on this dataset to generate more communication on the platform (like: "Thank you for downloading and using this data set. Please consider commenting the data in the "Discuss" section.)
However, for this, also guest users should be able to write comments as "guests"DD1 finalFelix HerrmannFelix Herrmann2024-05-26https://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/483upload of big files2024-01-12T10:00:03ZEduard Kleinupload of big filescheck if there are still problems with uploading big filescheck if there are still problems with uploading big filesDD1 finalFelix HerrmannFelix Herrmannhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/478refactor email sender2023-12-06T11:13:23ZStefan Hynekstefan.hynek@uni-goettingen.derefactor email sendershould be configurable from env; is currently hard coded to info@discuss-data.net, which is the address of the mailing list.should be configurable from env; is currently hard coded to info@discuss-data.net, which is the address of the mailing list.Stefan Hynekstefan.hynek@uni-goettingen.deStefan Hynekstefan.hynek@uni-goettingen.dehttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/475creating keywords2024-01-12T09:53:01ZEduard Kleincreating keywordsDringender Wunsch von Heiko:
Das Anlegen von Keywords sollte optimiert werden, evtl. auch die Kuratoren einbeziehen zur Überprüfung (Keyword Vorschlag), da viele Fehler: Keywords sollten sich pro Angabe auf ein Keyword beschränken (Komm...Dringender Wunsch von Heiko:
Das Anlegen von Keywords sollte optimiert werden, evtl. auch die Kuratoren einbeziehen zur Überprüfung (Keyword Vorschlag), da viele Fehler: Keywords sollten sich pro Angabe auf ein Keyword beschränken (Kommas/Semikolon löschen, in der Zukunft nicht mehr zulassen)DD1 finalFelix HerrmannFelix Herrmannhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/474data review2024-01-12T10:09:46ZEduard Kleindata reviewHeiko wünscht sich schon lange das "data review" feature, um Daten, die wo anders archiviert sind, dennoch zu besprechen. Mit Heiko und Ed genaue wünsche klären und die Eingabemaske absprechenHeiko wünscht sich schon lange das "data review" feature, um Daten, die wo anders archiviert sind, dennoch zu besprechen. Mit Heiko und Ed genaue wünsche klären und die Eingabemaske absprechenDD1 finalFelix HerrmannFelix Herrmann2024-05-26https://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/472issue with Lists2023-10-18T08:58:39ZEduard Kleinissue with ListsIf a user I follow saves a dataset to own of his lists, this info appears in my "dashboard". however, if a click on the list, the browser doesn't redirect me as the hyperlink is wrong: instead of a link to the list, I am redirected to th...If a user I follow saves a dataset to own of his lists, this info appears in my "dashboard". however, if a click on the list, the browser doesn't redirect me as the hyperlink is wrong: instead of a link to the list, I am redirected to the dashboard feed: https://discuss-data.net/users/feed/following/
Secondly, it might be useful the add a new tab in the dataset description, which shows, in which "lists" a certain dataset is - this might be helpful to find other related datasets (topic, research project etc.). This could be either shown as "The dataset is in list xyz..." or also as "User X has saved this dataset in his list y". This should be discussed in the team.DD1 finalhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/470Notification on access request2023-06-13T12:24:33ZFelix HerrmannNotification on access requestAccess Request notifications
- [x] should be send by email to requester and data owner
- [x] should include for data owner the URL to grant or decline access
- [x] should be shown in notifications tab
- [ ] should be auto-deleted after...Access Request notifications
- [x] should be send by email to requester and data owner
- [x] should include for data owner the URL to grant or decline access
- [x] should be shown in notifications tab
- [ ] should be auto-deleted after 2 or 4 weeks OR have a "resend request" function
- [ ] should include a text field for a message from requester to data owner
- [ ] send distinct emails with distinct text to curators w/o link
- [ ] change email text footer to: "Archiving, sharing and discussing research data on Eastern Europe, South Caucasus and Central Asia"
- [ ] limit time of access, provide choices dropdown (2 weeks, 6 months, a year, unlimited) with 6 months as default
see #437 and #421https://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/469add robots.txt2023-05-22T12:32:40ZStefan Hynekstefan.hynek@uni-goettingen.deadd robots.txtmissing robots configuration produces recurring and lots of errorsmissing robots configuration produces recurring and lots of errorshttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/465access request2024-03-06T14:45:00ZEduard Kleinaccess requestCurrently, if I want to access restricted files, I click on the button "Request access". The data depositor, who has to decide if his/her (sensitive) data can be accessed or not, do not know for what purpose and in which context the dat...Currently, if I want to access restricted files, I click on the button "Request access". The data depositor, who has to decide if his/her (sensitive) data can be accessed or not, do not know for what purpose and in which context the data will be used. Thus I suggest that you should not only click the button but also there should be a small text field where it should be described why the person needs access to the data (for a research article, out of interest, for commercial reasons etc.)
Also, we should think about the duration of the access: Currently, it does not expire, however, I would suggest that users have one month or so until the access expires - if they did not access it by then, they need to request it again - or what do you think?
Thirdly, as I curator I have access to restricted datasets of curated category; however in the tab "files", under the files themselves, I can still click on "request access" - which I already have; this must be changed in a message like: "As the curator of this category you automatically have access to this dataset"
![grafik](/uploads/6bde1b12e3072bfc5ecefc27bec56916/grafik.png)DD1 finalFelix HerrmannFelix Herrmannhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/464Add ORCID as experimental auth provider2024-01-12T10:08:44ZFelix HerrmannAdd ORCID as experimental auth providerauf Wunsch von Heiko nochmal Prio erhöht für HJ1 2024auf Wunsch von Heiko nochmal Prio erhöht für HJ1 2024DD1 finalFelix HerrmannFelix Herrmannhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/462Allow to add publications to a published dataset2023-10-18T08:44:27ZFelix HerrmannAllow to add publications to a published datasetPublications need to be added to an existing dataset, incrementing the version number on publication update makes no sense.
Solution: "unfreeze" publications tab after dataset publicationPublications need to be added to an existing dataset, incrementing the version number on publication update makes no sense.
Solution: "unfreeze" publications tab after dataset publicationDD1 finalhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/461Dashboard improvements2023-10-18T08:44:14ZFelix HerrmannDashboard improvements- [ ] Show the landing page news carousel in the dashboard
- [ ] Make "others activities" the default tab in the dashboard- [ ] Show the landing page news carousel in the dashboard
- [ ] Make "others activities" the default tab in the dashboardDD1 finalhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/457migrate to django 4.22023-12-04T12:16:50ZStefan Hynekstefan.hynek@uni-goettingen.demigrate to django 4.2currently used version 2.2.28 is EOL since April 11, 2022
help:
- https://docs.djangoproject.com/en/3.2/howto/upgrade-version/
- https://docs.djangoproject.com/en/3.2/releases/
especially:
- https://docs.djangoproject.com/en/3.2/releas...currently used version 2.2.28 is EOL since April 11, 2022
help:
- https://docs.djangoproject.com/en/3.2/howto/upgrade-version/
- https://docs.djangoproject.com/en/3.2/releases/
especially:
- https://docs.djangoproject.com/en/3.2/releases/3.0/#backwards-incompatible-changes-in-3-0DD1 finalhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/452change email address2023-12-11T16:15:38ZEduard Kleinchange email addressCurrently it is not possible to change the email, as it is linked with the Dariah-procedure.
However, as users over time change institutions, work with new email-addresses and lose access to their old ones, it must be possible for users ...Currently it is not possible to change the email, as it is linked with the Dariah-procedure.
However, as users over time change institutions, work with new email-addresses and lose access to their old ones, it must be possible for users to change their email address!DD1 finalFelix HerrmannFelix Herrmannhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/451Documentation: anonymization vs. hidden data in Excel files2022-12-20T14:12:08ZFelix HerrmannDocumentation: anonymization vs. hidden data in Excel fileshttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/448user profile information for non-registered users2023-10-18T08:35:10ZEduard Kleinuser profile information for non-registered usersWhile some user profiles are public and visible for every visitor, others are visible for registered users who are logged in.
If a non-registered user clicks to the profile of a user with a non-public account, a small message in the uppe...While some user profiles are public and visible for every visitor, others are visible for registered users who are logged in.
If a non-registered user clicks to the profile of a user with a non-public account, a small message in the upper right corner appears "The user has chosen not to share his profile details."
However, this notifaction is barely visible, and one might get the impression, the site doesn't work properly. It would be better to:
a) show the notification in the center or in a pop-up window
b) Instead of the current message "The user has chosen not to share his profile details." it should also contain the information that you can easily and quickly create your own free profile (with a link to the registration process) in order to access the information.DD1 finalhttps://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/447co-author rights/functions/visibility2024-01-12T09:52:03ZEduard Kleinco-author rights/functions/visibility@p.fherrma: Wünscht sich Heiko im 1HJ24!
currently, co-authors may be listed, but:
- they have no rights management for the data sets where they are co-authors, see for example this data-set: https://discuss-data.net/dataset/9211b92e-a...@p.fherrma: Wünscht sich Heiko im 1HJ24!
currently, co-authors may be listed, but:
- they have no rights management for the data sets where they are co-authors, see for example this data-set: https://discuss-data.net/dataset/9211b92e-a806-4e6c-ad75-d031a910b9f1/ Heiko Pleines is co-owner/author, but can't access the dataset himself!
- also, if they are registered users, the dataset should appear in their list of published data sets, but they are not listed there, see same example above: Heiko Pleines is co-author, but the data set is not listed in his dataset list: https://discuss-data.net/users/aee8d9d2-66b9-400c-a6d1-01484b6cdd04/datasets/ but the data should be linked with his profile as well!DD1 finalFelix HerrmannFelix Herrmann2024-05-26https://gitlab.gwdg.de/discuss-data/discuss-data/-/issues/444filter "access type" fehlt2023-10-18T08:58:07ZEduard Kleinfilter "access type" fehltEs sollte noch einen Filter geben nach access type:
- open access
- restricted access
- metadata only
um schnell alle open access daten vor allem anzeigen zu lassenEs sollte noch einen Filter geben nach access type:
- open access
- restricted access
- metadata only
um schnell alle open access daten vor allem anzeigen zu lassenDD1 final