Differences between revisions 2 and 3
Revision 2 as of 2008-09-12 12:11:42
Size: 1423
Editor: kfc
Comment:
Revision 3 as of 2008-09-12 21:57:39
Size: 1649
Editor: kfc
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
Uploading the file to bit storage must be done with the following API: Uploading the file to bit storage must be done with API calls for
Line 11: Line 11:
TODO: Need updated WSDL {{{
  uploadFile - in: filename,URLToFile,md5 out:characterizationOutput,fileName,fileUrl,md5,pronomId,validationStatus
  approveFile - in: fileUrl,md5
  disapproveFile - in: fileUrl,md5
  spaceLeft - out: bytes
}}}
WSDL: attachment:Bitstorage.xml

Bitstorage API

To add files to DOMS, three things will need to happen:

  • The file must be uploaded to bitstorage, and characterised
  • The file must be connected to a Fedora object datastream of type TypeFile

  • The characterisation output must be added to a Technical Metadata-stream in the object (the file and the characterisation result must match, see the data model documentation)

Uploading the file to bit storage must be done with API calls for

  uploadFile  - in: filename,URLToFile,md5 out:characterizationOutput,fileName,fileUrl,md5,pronomId,validationStatus
  approveFile - in: fileUrl,md5
  disapproveFile - in: fileUrl,md5
  spaceLeft - out: bytes

WSDL: attachment:Bitstorage.xml

Basically, you upload a file by presenting the bit storage resolvable URI, and the expected MD5 sum. The file will then be made available, and you will get a URI the file is stored on, and characteristica of the file back.

Those characteristica MUST be added in the proper places of the accompanying Fedora object.

Approve is used when the accompanying Fedora object is first sets published.

Disapprove is used if the accompanying Fedora object is marked deleted before publishing.

Examples

Adding a file and an accompanying fedora metadata object:

  • Make a new fedora object of type File in draft mode
  • Call upload on the bitstorage API
  • Add pronomid and characterisation to the appropriate datastreams
  • Set URL and MD5 on the CONTENT datastream

Publishing a file fedora object

  • Set fedora metadata objects to state "published"
  • Call approve from the bitstorage API

Bitstorage API (last edited 2010-03-17 13:09:38 by localhost)