-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #329 from ptsefton/use-cases-2024-07
Use cases 2024 07
- Loading branch information
Showing
11 changed files
with
856 additions
and
47 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,20 @@ | ||
--- | ||
page_id: arkisto | ||
redirect_from: | ||
- /in-use/arkisto | ||
title: Arkisto | ||
description: Arkisto uses RO-Crate for packaging data objects in the 3 uses cases described below, Modern PARADISEC, UTS Research Data Repository and UTS Cultural Datasets. As part of these use-cases they have been developing or enhancing their tooling to facilitate their use of RO-Crate | ||
description: Arkisto was a project website that aimed to outline a principled approach to research data management. | ||
url: https://arkisto-platform.github.io/ | ||
image: arkisto.png | ||
domains: [] | ||
tasks: [data_handling] | ||
roles: [data_steward, information_architect, repository_manager] | ||
--- | ||
|
||
## Arkisto | ||
|
||
The basis of Arkisto is that the long-term preservability of well-described data is always the first consideration. | ||
Data on an Arkisto deployment is alway available on disc (or object storage) with a complete description independently of any services such as websites or APIs. Once the data is safe and well described, Arkisto has a flexible model for how data can be accessed using a variety of services. | ||
Arkisto is built on top of Research Object Crate (RO-Crate) and the Oxford Common File System Layout (OCFL). | ||
With Arkisto there is no messy data migration. | ||
Arkisto was a project website that aimed to outline a principled approach to research data management. The site is no longer being maintained. | ||
|
||
The work done on Arkisto has been developed into a set of protocols: Protocols for Implementing Long-term Archival Repositories Services (PILARS) <http://w3id.org/ldac/pilars>. See the [RRKive](rrkive) and [PILARS](pilars) pages for more information. | ||
|
||
Arkisto was built on top of Research Object Crate (RO-Crate) and the Oxford Common File System Layout (OCFL). | ||
|
||
<img src="assets/img/arkisto.png" alt="Arkisto logo" width="300px"> |
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
page_id: pilars | ||
redirect_from: | ||
- /in-use/arkisto | ||
title: "PILARS" | ||
description: PILARS is a set of Protocols for Implementing Long-term Archival Repository Services | ||
url: https://w3id.org/ldac/pilars/ | ||
image: | ||
domains: [] | ||
tasks: [data_handling] | ||
roles: [data_steward, information_architect, repository_manager] | ||
--- | ||
|
||
# PILARS | ||
|
||
The Protocols for Implementing Long-term Archival Repository Services (PILARS, <http://w3id.org/ldac/pilars>) are inspired by the continuing success of the technical approach taken over two decades by [PARADISEC](paradisec). PARADISEC houses cultural heritage material from more than 1360 languages with standard metadata, with data stored in commodity services (initially files on disk, now objects in a cloud storage service), and metadata adjacent to the data. PILARS was developed through work with the Language Data Commons of Australia to generalise the PARADISEC approach to other disciplines. | ||
|
||
PILARS is aimed at IT practitioners, archivists, librarians, researchers and infrastructure managers involved in long-term data management. The protocols are intended to be complementary to the existing practices and principles of those disciplines. | ||
|
||
## Rationale | ||
|
||
In a research context it is important to be able to support the FAIR principles, ensuring that data is well described by metadata, is identified with persistent identifiers, and that shared services with good governance are in place to store interoperable data, to make it findable and provide appropriate access controls. | ||
|
||
These protocols could form the basis for design, evaluation or procurement of archival repository-services, but also allow for data custodians to begin organising data in a format ready for archiving and digital preservation as long as they have access to some kind of commodity storage, by using a range of tools. | ||
|
||
The PILARS Protocols call for the implementation of a linked-data metadata standard for describing data; RO-Crate represents one option for this. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
page_id: rrkive | ||
redirect_from: | ||
- /in-use/arkisto | ||
title: RRkive | ||
description: RRKive is a website aimed to outline a principled approach to research data management with guidance on data storage and metadata | ||
url: https://rrkive.org/ | ||
image: rrkive.png | ||
domains: [] | ||
tasks: [data_handling] | ||
roles: [data_steward, information_architect, repository_manager] | ||
--- | ||
|
||
# RRKive | ||
|
||
|
||
The RRKive site, managed by the Language Data Commons of Australia collects resources related to implementing Archival Repository ([RRKive](https://rkive.org/)) solutions based on a set of Protocols know as the PILARS: Principles for Implementing Long-term Archival Repository Services. https://w3id.org/ldac/pilars. RRkive is built on RO-Crate as a way to describe data objects for long term archiving. | ||
|
||
RRKive is a replacement for [Arkisto](arkisto). | ||
|
||
|
||
|
||
![RRKive logo is the word RRKive with a parrot sitting on it](assets/img/rrkive.png) |
Oops, something went wrong.