Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content placed in the "Terms of Access" field via dataset templates does not appear in datasets created with those templates #7217

Closed
BPeuch opened this issue Aug 21, 2020 · 8 comments

Comments

@BPeuch
Copy link
Contributor

BPeuch commented Aug 21, 2020

Version: 4.20

Greetings,

It seems that the field "Terms of Access" in the Terms section of a dataset cannot receive content from dataset templates. We've done several tests and the field always remains empty, whether a file was added to the dataset or not. We want to prepopulate it by the use of templates to inform depositors that, if they have chosen a template for datasets with restricted access, they must fill in the "Terms of Access" field.

Possibly related to #2565.

[Edit] I just ran a test to see if this problem also occurs in Demo Dataverse: it does.

@scolapasta
Copy link
Contributor

I was able to verify this - and that others Terms fields do copy (I tried a Data Access Place and Confidentiality Declaration.

I looked at the code and line 265 of TermsOfUseAndAccess.java (copyTermsOfUseAndAccess method) shows them being set, so something less obvious is clearly going on.

retVal.setTermsOfAccess(this.getTermsOfAccess());

@scolapasta
Copy link
Contributor

It's also true of the request access checkbox - my guess is that it's related to this. That both of these are getting unset because there are no files (no restricted files, in particular).

@scolapasta
Copy link
Contributor

More specifically, (and this is still just a guess), there's a popup on that page that sets both those fields (and shows up if you restrict files). So, the hypothesis is that it is replaces the values from the template with these empty values. The solution should be to populate the values into the popup (this also makes sense because when the popup comes up, these should default to the values from the template).

@BPeuch
Copy link
Contributor Author

BPeuch commented Sep 8, 2020

Thank you for your feedback @scolapasta! (And sorry for this late reaction. I was on holiday.)

@shlake
Copy link
Contributor

shlake commented Feb 17, 2021

Might be fixed in V 5.3??? Works OK in demo.dataverse.org (V5.3)

I have observed this in V5.2.....
Not sure if related, but if you do not enter "Terms of Access" when files are 1st restricted (via the popup) and then go back to "Edit Terms" to add text in "Terms of Access" the new text never appears. OR, if you want to change the "Terms of Access" from original, the new text does not get saved.

@scolapasta
Copy link
Contributor

scolapasta commented Feb 22, 2021

There have been issues related what @shlake is referring to, but as far as I know they are fixed in some version - i can't recall if in the released 5.3 or in a PR that is already merged in develop and slated for 5.4. (Offhand, I don't know if those fixes solve the problem for which this issue was opened).

@djbrooke
Copy link
Contributor

Hi - since we expect this is fixed in the current version, I'll close this issue. If we are wrong and it's still actually an issue, feel free to comment with details for it to be reopened. :)

@scolapasta
Copy link
Contributor

scolapasta commented Feb 23, 2021

I went ahead and refreshed my memory on the fixes I mentioned above; and tried in demo. All of the above should be working in 5.3. So as @djbrooke if you do see anything else related to this not working, let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants