...
- They each provide a means to read and write persistent files with unique ids.
- They were designed with back-end pluggability in mind.
- They are not concerned with directory/folder semantics.
- They are not concerned with versioning semantics, but may allow files to be overwritten.
The Basics
API | Type | Used By | Implementations | |||
|---|---|---|---|---|---|---|
Java | JackRabbit | |||||
Java | Cocoon | |||||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="dd7d98f1-ddef-4a5f-8a49-3a696795dac4"><ac:plain-text-body><![CDATA[ | [DSpace 2 BitStorehttp://wiki.dspace.org/index.php/DSpace_2.0/Pluggable_Storage] | Java | DSpace | DSBitStore | http://article.gmane.org/gmane.comp.db.dspace.user/3681] | ]]></ac:plain-text-body></ac:structured-macro> |
Java | Fedora Repo | Java | MediaWiki |
| ||
Java / C | * | FileNet? | ||||
Java | OTM |
| ||||
COM | MS SQL Server |
|
Supported Capabilities
- Ids
- Supported ID types?
- Can be store-generated?
- Can be user-provided?
- Readonly Metadata
- Which are impls expected to provide for reading?
- Settable Metadata
- Which are impls expected to provide for writing?
- Extensible?
- Transactional
- Supported by API?
- Required by impls?
- Two-phase commit?
...
- DSpace 1 BitstreamStorageManager - Hardcodes support for either local filesystem or SRB
- JAF FileDataSource - Assumes local files
- Eclipse - BlobStore- Assumes local paths and files
- MediaWiki FileStore - php? No source found.