Ever need to help a researcher share and archive their research data? Would you know how to advise them on managing their data so it can be easily shared and re-used? This workshop will cover best practices for collecting and organizing research data related to the goal of data preservation and sharing. We will focus on best practices and tips for collecting data, including file naming, documentation/metadata, quality control, and versioning, as well as access and control/security, backup and storage, and licensing. We will discuss the library’s role in data management, and the opportunities and challenges around supporting data sharing efforts. Through case studies we will explore a typical research data scenario and propose solutions and services by the library and institutional partners. Finally, we discuss methods to stay up to date with data management related topics.

The vrr extension for CKAN likely intends to enhance data resource management, specifically potentially related to versioning, revisions, or related resources. Given the limited information available in the readme, it is difficult to determine precise functionalities; however, based on naming conventions typically used in software development, the extension likely adds capabilities to track changes or dependencies between data resources within a CKAN instance. This would potentially assist users in maintaining data integrity and understanding data provenance. Key Features (assumed based on name and common patterns): Resource Relationships: Likely enables the creation and management of relationships between different resources, such as associating a derived dataset with its source data. Revision Tracking: Possibly tracks changes made to datasets and resources over time, allowing users to revert to previous versions or compare different versions. Versioning Support: Might implement a formal versioning system for datasets, enabling users to clearly identify and access specific versions of a dataset. Dependency Management: Potentially manages dependencies between datasets and other resources, ensuring that changes to one dataset do not break dependent datasets. Technical Integration: Due to minimal documentation, assuming integration through CKAN's plugin interface via changes to metadata schemas associated to the database and providing new API endpoints for managing resource relationships and providing versioning information. Further investigation would be required to establish precisely how the 'vrr' extension affects data structures and functionality. Benefits & Impact (assumed): Improved data governance and understandability by explicitly defining data provenance and relationships, potentially reducing errors and better facilitating data analysis and reproducibility. The extension has the potential to provide robust version tracking features, enabling data managers to comply with data management best practices.