Poster RDAP13: Research Data in eCommons @ Cornell: Present and Future
Upcoming SlideShare
Loading in...5
×
 

Poster RDAP13: Research Data in eCommons @ Cornell: Present and Future

on

  • 531 views

Wendy A. Kozlowski, Dianne Dietrich, Gail Steinhart and Sarah Wright ...

Wendy A. Kozlowski, Dianne Dietrich, Gail Steinhart and Sarah Wright
Cornell University Library, Ithaca, NY

Research Data in eCommons @ Cornell: Present and Future

Research Data Access & Preservation Summit 2013
Baltimore, MD April 4, 2013 #rdap13

Statistics

Views

Total Views
531
Views on SlideShare
528
Embed Views
3

Actions

Likes
0
Downloads
2
Comments
0

1 Embed 3

https://twitter.com 3

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Poster RDAP13: Research Data in eCommons @ Cornell: Present and Future Poster RDAP13: Research Data in eCommons @ Cornell: Present and Future Presentation Transcript

    • Research Data in eCommons @ Cornell: Present and FutureWendy A. Kozlowski*, Dianne Dietrich, Gail Steinhart and Sarah Wright     Cornell University Library, Ithaca, NY 14853     *wak57@cornell.eduAs funding agencies increasingly prioritizesharing of research data, the role of institutionalrepositories (IRs) to house this material is likelyto increase as well. By its very nature, data differsfrom the more traditional material housed in IRssuch as publications, presentations, theses anddissertations. Given these distinctions, an effortto optimize functionality of eCommons to handledata could be helpful to accommodate futuredata deposits. To evaluate what potentialeCommons users value in a repository forresearch data, we reviewed several sources ofresearcher feedback collected at CornellUniversity and elsewhere.IntroductionHow well are we meeting researcher needs and where can we go from here?33368716935737639347189812931528214432973385356267490 1000 2000 3000 4000 5000 6000 7000Animations and SoftwareMaps, Plans and BlueprintsDatasetsRecordings and Musical ScoresVideosLearning Objects and Fact SheetsPresentationsBooks or Book ChaptersOther (incl. Webpages and Websites)ArticlesBiographies and InterviewsPapers and ProjectsDissertations and ThesisTechnical Reports and PreprintsImagesJournalsSubmitter‐designated Item ʺTypesʺ in eCommons**data as of 27 Mar 2013; n = 24778 015304501000200030004000500060002002 2004 2006 2008 2010 2012eCommons SubmissionsTotal Items AddedItem Type ʺDatasetʺ AdditionsWhat does Cornell have?Cornell University Library’s IR, eCommons, is a DSpacepowered repository available for materials in digitalformats that may be useful for educational, scholarly,research or historical purposes. eCommons acceptsresearch data with file sizes up to 1GB and individualcollection sizes up to 10GB annually. By default, materialis openly accessible via the web and under certainsituations, access can be restricted to members of theCornell community only and/or embargoed for amaximum of 5 years. Entries are assigned a persistentidentifier (www.handle.net), and the CU Library iscommitted to preservation and to assuring long termaccess to contents. Upon deposit, users can assign anitem type; presently, “dataset” items represent less thanone half of one percent of total content (see figures, left).Datasets entries can be collections of multiple files;distribution of dataset file types is shown to the right..wav (4602).pdf (46).csv (56).txt (50) .doc (20).xls (14).qsf (1).wb2 (1)Entry type ʺdatasetʺ file extensionsWhat do researchers want?0 2 4 6 8Standardized metadataAbility of general public to easily find the datasetDocumentation of changes made to the dataset…Citation requirement for others when using datasetVersion controlData citation trackingAbility to cite the dataset in publicationsDiscovery of the dataset using Internet search…A basic, public description of and link to the data0 2 4 6 8Access restrictionsAbility of others to comment or annotateUsage/access statisticsTrack and show user commentsBatch uploadSelf‐submissionConnect to visualization or analytical toolsEasy transfer to permanent archiveConnect or merge data with other datasetsIn the spring of 2012, 8 faculty and stafffrom Cornell University (CU) andWashington University in St Louis wereinterviewed using a modified DataCuration Profile (DCP) Toolkit1.Researchers from a variety of disciplineswere asked to prioritize features relatedto repository functionality (shown atright). Results are generally consistentwith findings from a 2011 faculty surveyon data management needs2, DCPscompleted at other institutions3 and otherstudies on data sharing4.1 https://datacurationprofiles.org2 http://dx.doi.org/10.7191/jeslib.2012.10083 http://hdl.handle.net/1853/285094 doi:10.1371/journal.pone.0021101Key IR functions likely to be helpful to researchers Assessment of current eCommons support Considerations for the future of eCommons at CornellDiscoverability via standard Internet search engines Good, with some exceptions, such as incomplete indexing of large PDF’sIn addition to Internet discoverability, DSpace 3.1 will offer enhanced search and browse features within the IR; upgrade planned for summer 2013.Citation support (creation, export, tracking etc.) Not currently supported Explore creation of a suggested citation built in part from metadata; consider DOI assignment.Version Control Not currently supported Item level versioning  supported in DSpace 3.1.Self‐service submission Available; current active registered users: 968 (564 have submitted) Submission process may be additionally simplified using type‐based metadata fields.Access control by data owners Access can be limited to a CU subgroup and limited embargos are allowed Advanced embargo functionality supported in DSpace 3.1.Infrastructure to allow for dataset updates (due to changes or addition of new data)Datasets can be manually updated, but not without administrator support. Some datasets are updated by replacement, some by addition of new files.Clearly articulated best‐practices for dataset updates should be developed and added to eCommons usage policies.Linking between data sets and related publications  Not currently supportedDSpace does not allow for this functionality, but linkages using VIVO and a CU metadata repository (sites.google.com/site/datastarsite) are currently in development.