FW: REMINDER: Feedback on OCFL V2.0 Use Cases

[Arran Griffith]

Hi Everyone,

Forwarding on behalf of the OCFL community. Please read below for information on the use cases the Editors are considering including in the v2.0 release of the specification.

 

Cheers,

Arran

---

Arran Griffith

Program Manager, Fedora Program

Lyrasis

 

 

 

From: ocfl-co...@googlegroups.com <ocfl-co...@googlegroups.com> on behalf of Metz, Rosalyn <rosaly...@emory.edu>
Date: Thursday, February 15, 2024 at 1:13 PM
To: ocfl-co...@googlegroups.com <ocfl-co...@googlegroups.com>
Subject: [ocfl-community] REMINDER: Feedback on Use Cases

OCFL Community,

 

This is a reminder to review the list of potential use cases that might be addressed in version 2.0 of the specification. I’ve also included a list of all the use cases below. Note that there is a new use case for application profiles.

 

Issue #  Use Case Title

#50         Application Profiles

#47        External identifiers in place of digests                     

#46        Collapsing OCFL Object Versions

#48         Large Inventory.json files

#45        OCFL as a formal standard

#42        Support physical file-level deletion

#43        Defining a repository from peer storage roots

#39         Distributed Storage of objects and components

#44         OCFL Object Forking

#33         Package per version storage

#14         Flagging file loss/corruption

 

At the end of February, the OCFL Editors will start to look at prioritizing use cases and will communicate the results of those conversations to the community.

 

Best,

Rosalyn

 

------------------------------------

Rosalyn Metz

Chief Technology Officer

Emory Libraries and Museum

(o) 404.727.4680

(c) 404.831.8448

 

Pronouns: she/her/hers

--
You received this message because you are subscribed to the Google Groups "Oxford Common File Layout Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocfl-communit...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ocfl-community/PH0PR05MB984536760DA6828BF0DE559C904D2%40PH0PR05MB9845.namprd05.prod.outlook.com.

[Woods, Andrew]

Thanks for forwarding this message, Arran.

 

I would like to amplify and encourage you all to give the use cases a review. For those of you who are interested in the opportunity OCFL opens for retaining your storage root as the long-term, persistent bedrock of institutional data, you will be interested in:

#50 : Application Profiles

 

This use case introduces a mechanism (“application profiles”) for indicating how the files, naming conventions, metadata, relationships, structure, and so on that make up the “content” payload of your OCFL objects should be interpreted. Such “application profiles” are what will enable repository software that understands OCFL to also be able to understand how to interpret (i.e. read/write) the content therein. “Application profiles” will help unlock the potential of being able to keep your OCFL data the same while replacing over time the software that manages that data.

 

Best regards,

Andrew

--
You received this message because you are subscribed to the Google Groups "Fedora Committers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fedora-committ...@googlegroups.com.