cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.6084/m9.figshare.2002071
title: Leveraging VIVO to connect people, instruments, and data semantically in the geosciences: The UNAVCO case study

description: Preferred presentation format: Poster <br><br>UNAVCO is a non-profit university-governed consortium that facilitates geoscience research and education using geodesy. We plan to leverage and extend VIVO to enable the discovery of connections between people, data, and instrumentation. The UNAVCO case study is part of EarthCollab, a building block grant funded through the EarthCube Program at the National Science Foundation. The EarthCollab project includes a complementary case study at NCAR’s Earth Observing Laboratory (EOL). VIVO provides an attractive alternative to developing a new application in-house. VIVO is open source, can be modified to suit our use case, and has an active implementation and development community. <br><br>VIVO has primarily been utilized as a semantic profiling application for people. As an extendable semantic framework, however, it can be used to profile datasets and instruments. Notably, the Deep Carbon Observatory and the Laboratory for Atmospheric and Space Physics (LASP) have used modified implementations of VIVO to manage and display datasets. UNAVCO utilizes a wide variety of instrumentation, such as high precision GPS receivers, terrestrial laser scanning instruments, borehole strainmeters and other geodetic tools. No single existing ontology can describe our instrument arsenal or the large amounts of real time and archived data they produce adequately. We plan to extend the VIVO ontology’s limited support for datasets and instrumentation by incorporating parts of existing ontologies such as SWEET, DCAT, and GCIS, whenever possible. <br><br>UNAVCO is a geodetic facility that supports the research of external collaborators located at hundreds of institutions in the U.S. and abroad. We maintain over 2,000 instruments in the field. Additionally, we host and archive data, provide data services, have begun minting data DOIs, and offer instrument and data support to external researchers. We wish to use VIVO to display enhanced, up-to-date information about UNAVCO collaborators without the responsibility and resource commitment of being yet another canonical database store for their dynamic information, such as position titles and contact details. We will periodically ingest semantic data hosted at their home institution or at a third party (e.g. ORCID), which will be connected to our locally ingested information on datasets and instruments. <br><br>We have made significant progress ingesting datasets and publication data into VIVO. Next, we will finalize a set of ontological terms for instrument and dataset metadata. We will also develop a proof of concept implementation for sharing data between VIVO instances. Following the establishment of sustainable ingest methods, we will develop or adapt extensions to enhance discoverability of geoscience-specific information within VIVO.
DOI: 10.6084/m9.figshare.2002071.v2
title: Leveraging VIVO to connect people, instruments, and data semantically in the geosciences: The UNAVCO case study

description: Preferred presentation format: Poster <br><br>UNAVCO is a non-profit university-governed consortium that facilitates geoscience research and education using geodesy. We plan to leverage and extend VIVO to enable the discovery of connections between people, data, and instrumentation. The UNAVCO case study is part of EarthCollab, a building block grant funded through the EarthCube Program at the National Science Foundation. The EarthCollab project includes a complementary case study at NCAR’s Earth Observing Laboratory (EOL). VIVO provides an attractive alternative to developing a new application in-house. VIVO is open source, can be modified to suit our use case, and has an active implementation and development community. <br><br>VIVO has primarily been utilized as a semantic profiling application for people. As an extendable semantic framework, however, it can be used to profile datasets and instruments. Notably, the Deep Carbon Observatory and the Laboratory for Atmospheric and Space Physics (LASP) have used modified implementations of VIVO to manage and display datasets. UNAVCO utilizes a wide variety of instrumentation, such as high precision GPS receivers, terrestrial laser scanning instruments, borehole strainmeters and other geodetic tools. No single existing ontology can describe our instrument arsenal or the large amounts of real time and archived data they produce adequately. We plan to extend the VIVO ontology’s limited support for datasets and instrumentation by incorporating parts of existing ontologies such as SWEET, DCAT, and GCIS, whenever possible. <br><br>UNAVCO is a geodetic facility that supports the research of external collaborators located at hundreds of institutions in the U.S. and abroad. We maintain over 2,000 instruments in the field. Additionally, we host and archive data, provide data services, have begun minting data DOIs, and offer instrument and data support to external researchers. We wish to use VIVO to display enhanced, up-to-date information about UNAVCO collaborators without the responsibility and resource commitment of being yet another canonical database store for their dynamic information, such as position titles and contact details. We will periodically ingest semantic data hosted at their home institution or at a third party (e.g. ORCID), which will be connected to our locally ingested information on datasets and instruments. <br><br>We have made significant progress ingesting datasets and publication data into VIVO. Next, we will finalize a set of ontological terms for instrument and dataset metadata. We will also develop a proof of concept implementation for sharing data between VIVO instances. Following the establishment of sustainable ingest methods, we will develop or adapt extensions to enhance discoverability of geoscience-specific information within VIVO.
DOI: 10.6084/m9.figshare.2002032
title: Using Virtuoso as an alternate triple store for a VIVO instance

description: Background: For some time, the VIVO for Weill Cornell Medical College (WCMC) had struggled with both unacceptable page load times and unreliable uptime. With some individual profiles containing upwards of 800 publications, WCMC VIVO has relatively large profiles, but no profile was so large that it could account for this performance. The WCMC VIVO Implementation Team explored a number of options for improving performance including caching, better hardware, query optimization, limiting user access to large pages, using another instance of Tomcat, throttling bots, and blocking IP's issuing too many requests. But none of these avenues were fruitful. <br><br>Analysis of triple stores: With the 1.7 version, VIVO ships with the Jena SDB triple store, but the SDB version of Jena is no longer supported by its developers. In April, we reviewed various published analyses and benchmarks suggesting there were alternatives to Jena such as Virtuoso that perform better than even Jena's successor, TDB. In particular, the Berlin SPARQL Benchmark v. 3.1[1] showed that Virtuoso had the strongest performance compared to the other data stores measured including BigData, BigOwlim, and Jena TDB. In addition, Virtuoso is used on dbpedia.org which serves up 3 billion triples compared to the only 12 million with WCMC's VIVO site. Whereas Jena SDB stores its triples in a MySQL database, Virtuoso manages its in a binary file. The software is available in open source and commercial editions. <br> <br>Configuration: In late 2014, we installed Virtuoso on a local machine and loaded data from our production VIVO. Some queries completed in about 10% of the time as compared to our production VIVO. However, we noticed that the listview queries invoked whenever profile pages were loaded were still slow. After soliciting feedback from members of both the Virtuoso and VIVO communities, we modified these queries to rely on the OPTIONAL instead of UNION construct. This modification, which wasn't possible in a Jena SDB environment, reduced by eight-fold the number of queries that the application makes of the triple store. About four or five additional steps were required for VIVO and Virtuoso to work optimally with one another; these are documented in the VIVO Duraspace wiki. <br><br>Results: On March 31, WCMC launched Virtuoso in its production environment. According to our instance of New Relic, VIVO has an average page load of about four seconds and 99% uptime, both of which are dramatic improvements. There are opportunities for further tuning: the four second average includes pages such as the visualizations as well as pages served up to logged in users, which are slower than other types of pages. <br><br>[1] http://wifo5-03.informatik.uni-mannheim.de/bizer/berlinsparqlbenchmark/results/V7/#comparison
DOI: 10.6084/m9.figshare.2002029
title: Leveraging Institutional Data for Author Name Disambiguation

description: Author name disambiguation is a challenging problem in computer science. The problem arises from the fact that many authors share similar or identical names. Although some scholarly databases assign unique author identifiers, levels of accuracy are often unacceptable—especially for authors with common names. Existing algorithms have largely not leveraged institutional data on individual researchers. We are extending ReCiter, an agglomerative clustering algorithm for author name disambiguation, for use in publication management at our institution. The system uses available institutional data on researchers, including primary and secondary departments, history of co-investigatorships on grants and co-authorships, favored journals, and years of authors' terminal academic degrees. We are investigating the use of machine learning approaches to optimize system performance, and are planning to make the system available as a suite of freely available, open-source tools.
DOI: 10.6084/m9.figshare.2002032.v2
title: Using Virtuoso as an alternate triple store for a VIVO instance

description: Background: For some time, the VIVO for Weill Cornell Medical College (WCMC) had struggled with both unacceptable page load times and unreliable uptime. With some individual profiles containing upwards of 800 publications, WCMC VIVO has relatively large profiles, but no profile was so large that it could account for this performance. The WCMC VIVO Implementation Team explored a number of options for improving performance including caching, better hardware, query optimization, limiting user access to large pages, using another instance of Tomcat, throttling bots, and blocking IP's issuing too many requests. But none of these avenues were fruitful. <br><br>Analysis of triple stores: With the 1.7 version, VIVO ships with the Jena SDB triple store, but the SDB version of Jena is no longer supported by its developers. In April, we reviewed various published analyses and benchmarks suggesting there were alternatives to Jena such as Virtuoso that perform better than even Jena's successor, TDB. In particular, the Berlin SPARQL Benchmark v. 3.1[1] showed that Virtuoso had the strongest performance compared to the other data stores measured including BigData, BigOwlim, and Jena TDB. In addition, Virtuoso is used on dbpedia.org which serves up 3 billion triples compared to the only 12 million with WCMC's VIVO site. Whereas Jena SDB stores its triples in a MySQL database, Virtuoso manages its in a binary file. The software is available in open source and commercial editions. <br> <br>Configuration: In late 2014, we installed Virtuoso on a local machine and loaded data from our production VIVO. Some queries completed in about 10% of the time as compared to our production VIVO. However, we noticed that the listview queries invoked whenever profile pages were loaded were still slow. After soliciting feedback from members of both the Virtuoso and VIVO communities, we modified these queries to rely on the OPTIONAL instead of UNION construct. This modification, which wasn't possible in a Jena SDB environment, reduced by eight-fold the number of queries that the application makes of the triple store. About four or five additional steps were required for VIVO and Virtuoso to work optimally with one another; these are documented in the VIVO Duraspace wiki. <br><br>Results: On March 31, WCMC launched Virtuoso in its production environment. According to our instance of New Relic, VIVO has an average page load of about four seconds and 99% uptime, both of which are dramatic improvements. There are opportunities for further tuning: the four second average includes pages such as the visualizations as well as pages served up to logged in users, which are slower than other types of pages. <br><br>[1] http://wifo5-03.informatik.uni-mannheim.de/bizer/berlinsparqlbenchmark/results/V7/#comparison
DOI: 10.6084/m9.figshare.2002020
title: A RoadMap Process for VIVO

description: As an open source community, the VIVO Project relies on contributions of effort from its members. The VIVO strategic plan established the VIVO value proposition “VIVO provides an integrated view of the scholarly work of an organization” and two large scale goals supporting the value proposition: 1) Clarify and improve the value proposition; and 2) Promote a more open and networked research ecosystem. The roadmap process is designed to identify features and establish priorities that serve the value proposition and the strategic goals. The roadmap process follows basic principles of open source community development. First, it is open. All members of the community have an opportunity to participate in the roadmap process. Second, it serves the various constituents of the community. VIVO must serve end users, providing features that they can use in their daily work to advance scholarship. Data stewards and system administrators responsible for insuring local VIVO installations have quality data, and that the system accurately and effectively provides services to end-user must see improvement in VIVO relevant to their concerns. And finally, technologists, including developers, ontologists and committers must have environments and tools that support their productivity and creativity in enhancing VIVO. <br><br>In this poster we will present the VIVO roadmap process, describing its steps, its participants and the approach it takes to engaging the community and generating a prioritized set of features for future releases of VIVO. <br>
DOI: 10.6084/m9.figshare.2002029.v3
title: Leveraging Institutional Data for Author Name Disambiguation

description: Author name disambiguation is a challenging problem in computer science. The problem arises from the fact that many authors share similar or identical names. Although some scholarly databases assign unique author identifiers, levels of accuracy are often unacceptable—especially for authors with common names. Existing algorithms have largely not leveraged institutional data on individual researchers. We are extending ReCiter, an agglomerative clustering algorithm for author name disambiguation, for use in publication management at our institution. The system uses available institutional data on researchers, including primary and secondary departments, history of co-investigatorships on grants and co-authorships, favored journals, and years of authors' terminal academic degrees. We are investigating the use of machine learning approaches to optimize system performance, and are planning to make the system available as a suite of freely available, open-source tools.
DOI: 10.6084/m9.figshare.2002020.v2
title: A RoadMap Process for VIVO

description: As an open source community, the VIVO Project relies on contributions of effort from its members. The VIVO strategic plan established the VIVO value proposition “VIVO provides an integrated view of the scholarly work of an organization” and two large scale goals supporting the value proposition: 1) Clarify and improve the value proposition; and 2) Promote a more open and networked research ecosystem. The roadmap process is designed to identify features and establish priorities that serve the value proposition and the strategic goals. The roadmap process follows basic principles of open source community development. First, it is open. All members of the community have an opportunity to participate in the roadmap process. Second, it serves the various constituents of the community. VIVO must serve end users, providing features that they can use in their daily work to advance scholarship. Data stewards and system administrators responsible for insuring local VIVO installations have quality data, and that the system accurately and effectively provides services to end-user must see improvement in VIVO relevant to their concerns. And finally, technologists, including developers, ontologists and committers must have environments and tools that support their productivity and creativity in enhancing VIVO. <br><br>In this poster we will present the VIVO roadmap process, describing its steps, its participants and the approach it takes to engaging the community and generating a prioritized set of features for future releases of VIVO. <br>
DOI: 10.17608/k6.auckland.2001483
title: ISSP2013: National Identity III

description: The first International Social Survey Programme (ISSP) survey by COMPASS Research Centre at the University of Auckland, with funding support from its Business School. Three years after Professor Philip Gendall retired from contributing to the international programme, COMPASS worked to carry on this fine tradition, branding it locally as the Social Attitudes Survey New Zealand.Questions on national consciousness and national identity. Identification with town/city and nation; most important characteristics for national identity; perceived pride in the democracy of the country, the political influence of the country in the world, the economic achievement, the social security system, the scientific achievements, the achievements in sports, the achievements in arts or literature, the armed forces, the history and equal rights of all social groups in society.Attitude to the right of international institutions to enforce solutions to be accepted nationally; attitude to enforcing national interests regardless of evoking conflicts with other countries; rejection of acquisition of land by foreigners in the country; preference for national films in national television stations; damage done by large international companies to the local business; attitude to free trade; attitude to follow the decisions of international organisations even if the local government does not agree with them; international organisations take away too much power from the country. Availability of worldwide information as a benefit of the internet; importance of sharing national customs and traditions to achieve full nationality; attitude to government support of national minorities to preserve their customs and habits; preference for assimilation of minorities or retention of their identity; hostility to foreigners and prejudices against immigrants (scale); attitude to a reduction of immigration of foreigners; respondent’s citizenship; citizenship of parents at birth of respondent; same rights for citizens and legal immigrants; attitude towards stronger measures regarding illegal immigrants. Attitudes towards ethnic diversity in the workplace. Demography: Sex; age; marital status; steady life-partner; years in school, current employment status; current employment status of spouse; hours worked weekly; occupation of respondent and spouse; respondent and spouse working for private, public sector or self-employed; supervisor function; union membership; household size; family income; respondent’s earnings; vote last election; religious denomination; frequency of church attendance; region; town size, rural or urban region; ethnicity. Additionally encoded: mode of data collection.
DOI: 10.17608/k6.auckland.2001486
title: ISSP2014: Citizenship II

description: The second International Social Survey Programme (ISSP) survey by COMPASS Research Centre at the University of Auckland, with funding support from its Business School, and also the New Zealand European Union Centres Network, via colleagues at UoA and also Victoria University of Wellington.We were short on resources to run the survey in 2014, so this one was combined with the 2015 ISSP module on Work Orientations.A verbose rundown on topics covered follows.Qualities of a good citizen; social and political participation; group memberships; importance of different people’s rights in democracy (scale); estimation of political influence possibilities (political efficacy); likeliness of counter-action against an unjust law and expected chance of serious attention to people’s demand.Interest in politics; following of political news; personal trust in the political system; political discussions with friends; level of honesty and fairness in the last national election; corruption in public service; voter participation; voting behaviour (recall); attitudes to changing New Zealand flag.Qualities of being a New Zealander; ethnic vs. national identity; chances of leaving New Zealand in the next five years + reasons for this.Demography<br>Sex; age; marital-status; education; current employment status; hours worked weekly; occupation; working for private or public sector or self-employed; if self-employed: number of employees; supervisor function; trade union membership; current employment status; earnings; family income; household size; religious denomination; attendance of religious services; size of community; type of community: urban-rural area; ethnicity.
DOI: 10.4225/03/55c0653def745
title: Supporting data for systematic literature review

description: Data are results from a systematic literature review descibed in the papers submitted to PLOS ONE. Link to the papers will be provided once published.<br>
DOI: 10.17608/k6.auckland.2001483.v1
title: ISSP2013: National Identity III

description: TBCasdfasdfasdfadfsaa<br>asdf