Difference between revisions of "CDL Microservices and Ruby"
From Code4Lib
Line 16: | Line 16: | ||
Given that I have some image files | Given that I have some image files | ||
+ | |||
And the files already have names | And the files already have names | ||
+ | |||
Then I should be able to put the files somewhere | Then I should be able to put the files somewhere | ||
− | And I should be able to collect user-contributed | + | |
+ | And I should be able to collect user-contributed metadata | ||
+ | |||
And I should be able to track checksums for files | And I should be able to track checksums for files | ||
+ | |||
And I should be able to access content at persistent URLs | And I should be able to access content at persistent URLs |
Revision as of 15:18, 7 February 2011
Chris Beer's Microservices Ruby wrappers
- pairtree Now there's an official CDL pairtree implementation in ruby called orchard
- noid Identifier minting
- anvl A Name-Value Language "Basically like email headers"
- dflat Filesystem Convention for managing digital objects (maybe versioning too)
- checkm Manifest format ... Filename/checksum/createdate
- lockit File locking that is safe for Network filesystems
- namaste Name as Text -- file names on filesystems tell you something about what the directory contains
- microservices A Rails3 app that tries to put all of these pieces together (work in progress)
- bagit Bagit manifest format (from Library of Congress)
Use Case(s)
Given that I have some image files
And the files already have names
Then I should be able to put the files somewhere
And I should be able to collect user-contributed metadata
And I should be able to track checksums for files
And I should be able to access content at persistent URLs