add fulltext to publications bibtex, switch around button placement

This commit is contained in:
Vicky Rampin 2021-04-22 19:24:11 -04:00
parent 7ac87716cb
commit c83f064e5b
3 changed files with 45 additions and 23 deletions

View File

@ -7,6 +7,7 @@
booktitle = {{Hawaii International Conference on System Sciences}}, booktitle = {{Hawaii International Conference on System Sciences}},
month = jan, month = jan,
year = {2021}, year = {2021},
fulltext={http://hdl.handle.net/10125/71493}
} }
@article{rampin_reproserver:_2018, @article{rampin_reproserver:_2018,
@ -18,6 +19,8 @@
author = {Rampin, Remi and Chirigati, Fernando and Steeves, Vicky and Freire, Juliana}, author = {Rampin, Remi and Chirigati, Fernando and Steeves, Vicky and Freire, Juliana},
month = aug, month = aug,
year = {2018}, year = {2018},
fulltext={http://arxiv.org/abs/1808.01406}
} }
@article{wolke_reproducible_2016, @article{wolke_reproducible_2016,
@ -34,6 +37,7 @@
month = jul, month = jul,
year = {2016}, year = {2016},
pages = {98--101}, pages = {98--101},
fulltext={https://arxiv.org/abs/1703.00042}
} }
@article{rampin_reprozip:_2016, @article{rampin_reprozip:_2016,
@ -50,6 +54,8 @@
year = {2016}, year = {2016},
doi = {10.21105/joss.00107}, doi = {10.21105/joss.00107},
pages = {107}, pages = {107},
abstract={{ReproZip is a tool aimed at simplifying the process of creatingreproducible experiments. After finishing an experiment, writing a website, constructinga database, or creating an interactive environment, users can run ReproZip to createreproducible packages, archival snapshots, and an easy way for reviewers to validate theirwork.}},
fulltext={http://joss.theoj.org/papers/10.21105/joss.00107}
} }
@article{steeves_reproducibility_2017, @article{steeves_reproducibility_2017,
@ -63,6 +69,8 @@
author = {Steeves, Vicky}, author = {Steeves, Vicky},
month = jul, month = jul,
year = {2017}, year = {2017},
abstract = {{Over the past few years, research reproducibility has been increasingly highlighted as a multifaceted challenge across many disciplines. There are socio-cultural obstacles as well as a constantly changing technical landscape that make replicating and reproducing research extremely difficult. Researchers face challenges in reproducing research across different operating systems and different versions of software, to name just a few of the many technical barriers. The prioritization of citation counts and journal prestige has undermined incentives to make research reproducible. While libraries have been building support around research data management and digital scholarship, reproducibility is an emerging area that has yet to be systematically addressed. To respond to this, New York University (NYU) created the position of Librarian for Research Data Management and Reproducibility (RDM & R), a dual appointment between the Center for Data Science (CDS) and the Division of Libraries. This report will outline the role of the RDM & R librarian, paying close attention to the collaboration between the CDS and Libraries to bring reproducible research practices into the norm.}},
fulltext={https://digitalcommons.du.edu/collaborativelibrarianship/vol9/iss2/4}
} }
@article{johnson_research_2019, @article{johnson_research_2019,
@ -77,6 +85,8 @@
author = {Johnson, Kelly and Steeves, Vicky}, author = {Johnson, Kelly and Steeves, Vicky},
month = oct, month = oct,
year = {2019}, year = {2019},
abstract={{Objective: This paper aims to inform on opportunities for librarians to assist faculty with research data management by examining practices and attitudes among life sciences faculty at a tier one research university. Methods: The authors issued a survey to estimate actual and perceived research data management needs of New York University (NYU) life sciences faculty in order to understand how the library could best contribute to the research life cycle. Results: Survey responses indicate that over half of the respondents were aware of publisher and funder mandates, and most are willing to share their data, but many indicated they do not utilize data repositories. Respondents were largely unaware of data services available through the library, but the majority were open to considering such services. Survey results largely mimic those of similar studies, in that storing data (and the subsequent ability to share it) is the most easily recognized barrier to sound data management practices. Conclusions: At NYU, as with other institutions, the library is not immediately recognized as a valuable partner in managing research output. This study suggests that faculty are largely unaware of, but are open to, existent library services, indicating that immediate outreach efforts should be aimed at promoting them.}},
fulltext={https://escholarship.umassmed.edu/jeslib/vol8/iss1/}
} }
@article{steeves_reproducibility_2020, @article{steeves_reproducibility_2020,
@ -94,6 +104,8 @@
year = {2020}, year = {2020},
note = {Number: 1-2}, note = {Number: 1-2},
pages = {1--11}, pages = {1--11},
abstract={{The adoption of reproducibility remains low, despite incentives becoming increasingly common in different domains, conferences, and journals. The truth is, reproducibility is technically difficult to achieve due to the complexities of computational environments. To address these technical challenges, we created ReproZip, an open-source tool that automatically packs research along with all the necessary information to reproduce it, including data files, software, OS version, and environment variables. Everything is then bundled into an rpz file, which users can use to reproduce the work with ReproZip and a suitable unpacker (e.g.: using Vagrant or Docker). The rpz file is general and contains rich metadata: more unpackers can be added as needed, better guaranteeing long-term preservation. However, installing the unpackers can still be burdensome for secondary users of ReproZip bundles. In this paper, we will discuss how ReproZip and our new tool, ReproServer, can be used together to facilitate access to well-preserved, reproducible work. ReproServer is a web application that allows users to upload or provide a link to a ReproZip bundle, and then interact with/reproduce the contents from the comfort of their browser. Users are then provided a persistent link to the unpacked work on ReproServer which they can share with reviewers or colleagues.}},
fulltext={https://iassistquarterly.com/index.php/iassist/article/view/969}
} }
@article{steeves_using_2018, @article{steeves_using_2018,
@ -110,6 +122,8 @@
year = {2018}, year = {2018},
note = {Number: 1}, note = {Number: 1},
pages = {14--14}, pages = {14--14},
abstract={{Achieving research reproducibility is challenging in many ways: there are social and cultural obstacles as well as a constantly changing technical landscape that makes replicating and reproducing research difficult. Users face challenges in reproducing research across different operating systems, in using different versions of software across long projects and among collaborations, and in using publicly available work. The dependencies required to reproduce the computational environments in which research happens can be exceptionally hard to track in many cases, these dependencies are hidden or nested too deeply to discover, and thus impossible to install on a new machine, which means adoption remains low. In this paper, we present ReproZip , an open source tool to help overcome the technical difficulties involved in preserving and replicating research, applications, databases, software, and more. We will examine the current use cases of ReproZip , ranging from digital humanities to machine learning. We also explore potential library use cases for ReproZip, particularly in digital libraries and archives, liaison librarianship, and other library services. We believe that libraries and archives can leverage ReproZip to deliver more robust reproducibility services, repository services, as well as enhanced discoverability and preservation of research materials, applications, software, and computational environments.}},
fulltext={https://www.iassistquarterly.com/index.php/iassist/article/view/18}
} }
@inproceedings{boss_saving_2019, @inproceedings{boss_saving_2019,
@ -123,6 +137,7 @@
author = {Boss, Katherine E. and Steeves, Vicky and Rampin, Remi and Chirigati, Fernando and Hoffman, Brian}, author = {Boss, Katherine E. and Steeves, Vicky and Rampin, Remi and Chirigati, Fernando and Hoffman, Brian},
month = sep, month = sep,
year = {2019}, year = {2019},
fulltext={https://osf.io/preprints/lissa/khtdr/}
} }
@inproceedings{blumenthal_what_2016, @inproceedings{blumenthal_what_2016,
@ -136,6 +151,7 @@
author = {Blumenthal, Karl-Rainer and Griesinger, Peggy and Kim, Julia and Peltzman, Shira and Steeves, Vicky}, author = {Blumenthal, Karl-Rainer and Griesinger, Peggy and Kim, Julia and Peltzman, Shira and Steeves, Vicky},
month = oct, month = oct,
year = {2016}, year = {2016},
fulltext = {https://osf.io/preprints/lissa/tnmra/}
} }
@article{blumenthal_whats_2020, @article{blumenthal_whats_2020,
@ -149,4 +165,6 @@
author = {Blumenthal, Karl and Griesinger, Peggy and Kim, Julia and Peltzman, Shira and Steeves, Vicky}, author = {Blumenthal, Karl and Griesinger, Peggy and Kim, Julia and Peltzman, Shira and Steeves, Vicky},
month = aug, month = aug,
year = {2020}, year = {2020},
abstract={{The National Digital Stewardship Alliance surveyed practitioners in 2012 and again in 2017 to gauge, among other things, how satisfied they were with their organizations digital preservation function. This study seeks to understand what causes the high and rising levels of dissatisfaction that practitioners reported. We interviewed 21 digital stewards and asked them to describe the organizational context in which they work; to reflect on what aspects of their organizations approach to digital preservation are working well and which are not; and to evaluate necessary areas of improvement. We identified experiences that were common among participants using a qualitative research methodology based on phenomenology. These conversations revealed that practitioners largely consider digital stewardship values and goals to be misunderstood at an organizational level, and demonstrated that the absence of a long-term vision for digital stewardship disempowers practitioners.}},
fulltext = {https://elischolar.library.yale.edu/jcas/vol7/iss1/13}
} }

View File

@ -151,18 +151,7 @@ class PublicationList(Directive):
extra_links = "" extra_links = ""
if 'fulltext' in entry.fields: # the link to the full text, usually a link to the pdf file
extra_links += '[<a href="{}">full text</a>] '.format(entry.fields['fulltext'])
bibtex_fields = dict(entry.fields) bibtex_fields = dict(entry.fields)
# Collect and remove custom links (fields starting with "customlink")
custom_links = dict()
for key, value in bibtex_fields.items():
if key.startswith('customlink'):
custom_links[key[len('customlink'):]] = value
# custom fields (custom links)
for key, value in custom_links.items():
extra_links += '[<a href="{}">{}</a>] '.format(value, key)
# Remove some fields for the publicly available BibTeX file since they are mostly only # Remove some fields for the publicly available BibTeX file since they are mostly only
# used by this plugin. # used by this plugin.
@ -188,6 +177,20 @@ class PublicationList(Directive):
}} }}
}})(this, '{}');">BibTeX&#x25BC;</a>] }})(this, '{}');">BibTeX&#x25BC;</a>]
'''.format('bibtex-' + label) '''.format('bibtex-' + label)
if 'fulltext' in entry.fields: # the link to the full text, usually a link to the pdf file
extra_links += '[<a href="{}">Full Text ⬈</a>] '.format(entry.fields['fulltext'])
# Collect and remove custom links (fields starting with "customlink")
custom_links = dict()
for key, value in bibtex_fields.items():
if key.startswith('customlink'):
custom_links[key[len('customlink'):]] = value
# custom fields (custom links)
for key, value in custom_links.items():
extra_links += '[<a href="{}">{} ⬈</a>] '.format(value, key)
if bibtex_dir: # write bib files to bibtex_dir for downloading if bibtex_dir: # write bib files to bibtex_dir for downloading
bib_link = '{}/{}.bib'.format(bibtex_dir, label) bib_link = '{}/{}.bib'.format(bibtex_dir, label)
bib_data.to_file('/'.join([self.output_folder, bib_link]), 'bibtex') bib_data.to_file('/'.join([self.output_folder, bib_link]), 'bibtex')
@ -203,14 +206,14 @@ class PublicationList(Directive):
if ($('#' + id).css('display') == 'block') if ($('#' + id).css('display') == 'block')
{{ {{
$('#' + id).hide('fast'); $('#' + id).hide('fast');
$(target).text('abstract&#x25BC;') $(target).text('Abstract&#x25BC;')
}} }}
else else
{{ {{
$('#' + id).show('fast'); $('#' + id).show('fast');
$(target).text('abstract&#x25B2;') $(target).text('Abstract&#x25B2;')
}} }}
}})(this, '{}');">abstract&#x25BC;</a>] '''.format('abstract-' + label) }})(this, '{}');">Abstract&#x25BC;</a>] '''.format('abstract-' + label)
display_none = '<div id="{}" style="display:none"><pre>{}</pre></div>' display_none = '<div id="{}" style="display:none"><pre>{}</pre></div>'
bibtex_display = display_none.format( bibtex_display = display_none.format(
@ -220,7 +223,7 @@ class PublicationList(Directive):
LaTeXParser(entry.fields['abstract']).parse()) if 'abstract' in entry.fields else '' LaTeXParser(entry.fields['abstract']).parse()) if 'abstract' in entry.fields else ''
if detail_page_dir: # render the details page of a paper if detail_page_dir: # render the details page of a paper
page_url = '/'.join((detail_page_dir, label + '.html')) page_url = '/'.join((detail_page_dir, label + '.html'))
html += '[<a href="{}">details</a>] '.format( html += '[<a href="{}">Details</a>] '.format(
self.site.config['BASE_URL'] + page_url) self.site.config['BASE_URL'] + page_url)
context = { context = {
'title': str(LaTeXParser(entry.fields['title']).parse()), 'title': str(LaTeXParser(entry.fields['title']).parse()),

View File

@ -34,20 +34,21 @@ import os, mako
</header> </header>
<div class="reference"> <div class="reference">
<p>
{{ reference }}
{% if extra_links %}
<br/>{{ extra_links }}
{% endif %}
</p>
</div>
{% if abstract %} {% if abstract %}
<h2>Abstract</h2> <h2>Abstract</h2>
<div class="publication-abstract"> <div class="publication-abstract">
<p>{{ abstract | h }}</p> <p>{{ abstract | h }}</p>
</div> </div>
{% endif %} {% endif %}
<p>
{{ reference }}
{% if extra_links %}
<br/>{{ extra_links }}
{% endif %}
</p>
</div>
{{ include_if_exists("publicationlist_{ }_after_abstract.html".format(label))}} {{ include_if_exists("publicationlist_{ }_after_abstract.html".format(label))}}