-
Notifications
You must be signed in to change notification settings - Fork 490
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
Datafile suggested citation doesn't include file DOI #4777
Comments
Per discussion in #2438 and on the community group (https://groups.google.com/forum/#!msg/dataverse-community/ZY53hidy-MU/MaU2YtJUBwAJ), it sounds like the idea of including both the dataset and file DOI in the citation was not a desired solution. It may still be an open question whether a direct data file citation is desirable as an alternative to citing the dataset and mentioning the file... |
@scolapasta you mentioned yesterday in backlog grooming that there were a few options for moving forward here. Assigning to you for the specifics. @qqmyers - do you have any availability to pick this up once we get feedback from the Community + @mercecrosas and others about what we want to do here? |
@djbrooke - I think so. Looks like the latest discussion is along the lines of the image below. In testing how to do this, I realized that the code for the endnote, ris, and bibtex downloads has to be modified as well... (and the help link to data citation practices might need to move so it is not repeated.) |
@qqmyers thanks for making pull request #4802! I just dragged this issue to code review at https://waffle.io/IQSS/dataverse |
Copying/expanding some notes from the discussion forum w.r.t. the screenshot above: The text outside the blue citation boxes is in Bundle.properties and since the screen capture, the initial PR simplifies the default to:
QDR also uses '. ' instead of ', ' as a separator - the PR uses a String set to ', ' which makes customizing for QDR easier, but doesn't pull this out as a Bundle option or key. With these changes the citations above would look like: Myers, Jim, 2018, "QDR-982 testing", https://doi.org/10.5072/FK2DQKOMA. QDR Main Collection. V1; court dare.jpg [fileName] Myers, Jim, 2018, "court dare.jpg", QDR-982 testing, https://doi.org/10.5072/FK2DQKOMA/48ZYBJ, QDR Main Collection, V1 Note - my example file doesn't have a UNF - a file with one would have it appended in both citation forms as it is in the 4.9.q release. |
It was driving me crazy that DataCitation.java had zero code coverage among it's 623 lines so I pushed a test in 4c67e61 to increase it to 24%. I don't want to hold up QA but in the future I hope we can add more tests. BeforeAfter |
@qqmyers can you make a small change to the text? I ran this by Merce to check on on the citation formats / labels, and since the first citation includes the file details, it's better to say: |
Thinking more about this, I'm not convinced what we're doing with this is optimal. As of now we have three different citations:
with 1 on the dataset landing page, 2 and 3 on the data file landing page. Logically these also correspond to three different sets of metadata. I think that's very confusing. With two different versions of a file citation on the file landing page, it's also unclear which of them should be encoded in schema.org metadata on that page. I would suggest, instead, to make 1. and 2. identical, so we have
In other words, get rid of the [file name] at the end of the dataset citation on file landing pages. If people want to cite a specific file, they should just use 2. In the more common case, where they're looking at a file but really mean to cite the whole dataset, we should have 1. available on the file landing page (as per the discussion in the community group). Thoughts? To illustrate:(recall that QDR uses "data project" instead of "dataset") |
@mercecrosas thoughts on @adam3smith's comment? (this is related to one of our recent discussions) |
No, I haven't yet -- happy to check. |
@mercecrosas -- haven't heard back from Martin. Do you have any other thoughts on who to ask? My view would be to just go ahead with this change. I tried to look for standards and practices on file citations when I made the original proposal and didn't find anything at all. |
Yes, that makes sense to me, too. |
depending on whether the file has a DOi or not, per IQSS#4777 (comment)
depending on whether the file has a DOi or not, per IQSS#4777 (comment) Conflicts: src/main/java/edu/harvard/iq/dataverse/DataCitation.java
The status of this issue wasn't immediately clear to me so here's a screenshot of the conversation from #4971 (review) I put it back into code review because that seems to be the right spot. |
@qqmyers
[2018-08-24T18:47:30.003-0400] [glassfish 4.1] [WARNING] [AS-EJB-00056] [javax.enterprise.ejb.container] [tid: _ThreadID=50 _ThreadName=jk-connector(1)] [timeMillis: 1535150850003] [levelValue: 900] [[ [2018-08-24T18:47:30.003-0400] [glassfish 4.1] [WARNING] [] [javax.enterprise.ejb.container] [tid: _ThreadID=50 _ThreadName=jk-connector(1)] [timeMillis: 1535150850003] [levelValue: 900] [[ javax.ejb.EJBException |
|
|
Thanks @adam3smith and @qqmyers for the information and the fix! |
@qqmyers OK, confirmed RIS download is working, thanks. Noticed italicized title is now normal text in file citation. Was that changed? We are taking @adam3smith advice on this and are fine with italicized. Nevermind, it becomes italicized upon publishing. My bad! |
@kcondon - I didn't change the italics. It does only apply to published files where the citation includes the file title then the dataset title in italics versus the file title being appended for unpublished ones. |
Spoke with @adam3smith about the citation styles for files versus datasets. Bit of a puzzle. He pointed out that for most citation styles, when the citation includes two objects, like a chapter and the book that the chapter is in, the secondary object (like the book) is never in quotes (see some examples). In other words, when the object being referenced (like a file) is part of a larger work (a dataset), the larger work is never in quotes; if the work being referenced (like the file) is. So keeping the dataset title in quotes when it's in the file citation would break that rule and may confuse users (and might make it more difficult for software to create citations?). He used italics for the dataset title instead so that the secondary object is styled differently, so that there's another distinction between the file title and dataset title. But because the dataset title of the dataset citation IS in quotes, this means that the dataset title won't be styled the same when it's in a file citation. One solution is to use something other than quotes for the dataset title in the dataset citation, but this would change Dataverse's dataset citation style. |
The suggested citation that appears on a 4.9 datafile page is currently just the suggested citation for the dataset with the file name and the text'[filename]' postpended. With file DOIs now being generated, it seems like the suggested citation should be updated, e.g. to postpend the file name and file DOI for example. An alternative would be to change the whole citation to just reference the file (which would require changing the text 'This file is part of "". If you use this file, please cite the data project:' that is directly above the citation block). I personally think that keeping the citation focused on the dataset and just adding the filename and DOI is a good approach, but I don't know if that would work for everyone/if this needs to be a config option, etc.
The text was updated successfully, but these errors were encountered: