...
Content resources are identified by a file name. In most cases, this name will have a file extention separated by a period, from which the MIME type may be deduced (via an extention map). All files also have a metadata file associated with it named the same, with a file extension of .properties. These properties may optionally be cached in a database to allow faster access to them.
Resources may have attachements - TBD.attachemnts - how will these be identified? How will they be kept together with their resource?
All resources (and attachments) live in a collection. Resource identifiers must be unique within the collection they live in. Collections may contain sub-collections. Collections are simply named and correspond to directories in a file system. Collection names must be unique within the collection they live in.
Collection paths are defined against a local root. This root is associated with a context (usually a site). Local roots branch from a Sakai global root, which in turn is mapped to a file system location.
Things To Do
Item | Status | Notes |
|---|---|---|
Resource metadata |
|
|
Collection metadata |
|
|
Attachments |
| Need to figure out how to include these. |
Attachment metadata |
|
|
File types |
| Need a mapping function. |
Drop Box |
Issues
- Properties can only store string-based properties.
Project Status
...
| Has this been changed for 2.2? |
Project Status
Based implementation of resources and collections have begun. Interfaces have been copied locally to the ContentTool to simplify things for the interrim. As the implementations approach the full API specifications, the real APIs will be referenced. This is especially true of the ContentHostingService, which has many, many methods.
The APIs are sorta mid-way between Sakai 2.1 and 2.2. I need to create a sandbox in the 2.2 world and start referring to the new package names for ContentHosting. I'm holding off until I do the initial check in to contrib before making these changes.
Note: Sakai 2.2 defines a ContentEntity.
ContentHostingService Methods
...
Method Name | Status | Notes |
|---|---|---|
isActiveEdit(); |
|
|
getPropertiesEdit(); |
|
|
|
|
|
setReleaseDate(); |
| 2.2 method |
setRetractDate(); |
| 2.2 method |
ContentResource Methods
...
Method Name | Status | Notes |
|---|---|---|
getUrl(); |
|
|
getReference(); |
|
|
getUrl(root-prop); |
|
|
getReference(root-prop); |
|
|
getId(); |
|
|
getProperties(); |
|
|
toXml(); |
|
|
|
|
|
getContentLength(); |
|
|
String getContentType(); |
|
|
getContent(); |
|
|
getReleaseDate(); |
| 2.2 method |
getRetractDate(); |
| 2.2 method |
streamContent(); |
|
|
...