Difference between revisions of "CDL Microservices and Ruby"
From Code4Lib
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Chris Beer's Microservices Ruby wrappers | Chris Beer's Microservices Ruby wrappers | ||
| − | * [http://github.com/cbeer/pairtree | + | * [http://github.com/cbeer/pairtree pairtree] Now there's an official CDL pairtree implementation in ruby called [https://github.com/cdlib/orchard orchard] |
| − | * [http://github.com/cbeer/noid | + | * [http://github.com/cbeer/noid noid] Identifier minting |
| − | * [http://github.com/cbeer/anvl | + | * [http://github.com/cbeer/anvl anvl] A Name-Value Language "Basically like email headers" |
| − | * [http://github.com/cbeer/dflat | + | * [http://github.com/cbeer/dflat dflat] Filesystem Convention for managing digital objects (maybe versioning too) |
| − | * [http://github.com/cbeer/checkm | + | * [http://github.com/cbeer/checkm checkm] Manifest format ... Filename/checksum/createdate |
| − | * [http://github.com/cbeer/lockit | + | * [http://github.com/cbeer/lockit lockit] File locking that is safe for Network filesystems |
| − | * [http://github.com/cbeer/namaste | + | * [http://github.com/cbeer/namaste namaste] Name as Text -- file names on filesystems tell you something about what the directory contains |
| − | * [https://github.com/cbeer/microservices | + | * [https://github.com/cbeer/microservices microservices] A Rails3 app that tries to put all of these pieces together (work in progress) |
| − | * [https://github.com/flazz/bagit | + | * [https://github.com/flazz/bagit bagit] Bagit manifest format (from Library of Congress) |
'''Use Case(s)''' | '''Use Case(s)''' | ||
| − | + | <pre> | |
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 | ||
| Line 22: | Line 22: | ||
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 | ||
| − | + | </pre> | |
| + | |||
| + | '''needed''' | ||
| + | |||
| + | * graphical metadata editing and generation of filesystem | ||
| + | * fixity service | ||
| + | * inventory and solr ingestion | ||
| + | |||
| + | fork of cbeer's microservices demonstrator: [https://github.com/jronallo/microservices] | ||
Latest revision as of 16:41, 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
needed
- graphical metadata editing and generation of filesystem
- fixity service
- inventory and solr ingestion
fork of cbeer's microservices demonstrator: [1]
