First of all, thanks for the reply and the answer.

On Fri, Aug 14, 2009 at 8:56 PM, Chris Wilper <[email protected]> wrote:

> Hi Matteo,
>
> When ingesting an object with managed content, you have a couple
> options.  One is to provide it in base64 format inside the FOXML
> itself.  (export an object with some managed content in the "archive"
> context to see an example).  The other option is to provide it by
> reference.  With this option, you give it an HTTP URL (you have to
> have a webserver fronting the content) and Fedora copies the content
> into the repository at ingest time.
>
> More detail:
>
> For managed content, the way content is included (or referenced)
> within FOXML depends on a couple factors.
>
> If the FOXML is about to be ingested, managed datastreams can be
> included as base64-encoded content right inside the XML.  It can also
> be referenced via URL (http).  In the latter case, Fedora retrieves
> the content automatically as part of the ingest operation.


 I fear I can not use such an option, sice I have someting like 1M objects,
each with a few Mbytes datastream associated.


>
> If the object is inside the repository already, managed content is
> referenced within the FOXML in using a special kind of reference (e.g.
> "changeme:6+DS1+DS1.0").  This kind of reference is only used inside
> the repository to get the content from the appropriate place (the low
> level file storage) when appropriate.


So, in the FOXML I should have a line that reads "<foxml:contentLocation
REF="changeme:6+DS1+DS1.0"....
Is this correct ?



> You typically don't use or
> create these kind of references.


why ? In my naiveness, I thought this might be useful, at least for my
purposes: I havve all datastreams already on server, I create a batch XML,
all the objects XML and then ingest them, with the datastreams already in
the server.


>
>
> When exporting FOXML, you have a choice of "contexts".  In the
> "archive" context, the managed content is included within the FOXML
> itself.  In the "public" or "migrate" context, the managed content is
> referenced via URL (e.g.
> "http://XXXXXX:8080/fedora/get/changeme:6/DS1/2009-08-10T07:29:22.068Z";).
>
> - Chris
>
> On Thu, Aug 13, 2009 at 9:04 AM, Matteo
> Boschini<[email protected]> wrote:
> > (sorry for re-posting, something must hav gone wrong with previous
> post...)
> > Hello all,
> >
> > I', still new to fedora, so please bear with me.
> > I'm trying to write my own FOXML (1.1) file in order to ingest via client
> > command line some digital objects.
> > I'm fine as long as the datastreams are "R"(eridect) or "E"(xternal), but
> it
> > seems I can not use some M type.
> > I tried to ingest the object via client/fedora-admin, and that's ok, but
> > when I look at the exported FOXML, I get something like
> >
> > <foxml:contentLocation
> > REF="
> http://XXXXXX:8080/fedora/get/changeme:6/DS1/2009-08-10T07:29:22.068Z
> >
> > According to FOXML reference example
> > (
> http://www.fedora-commons.org/confluence/download/attachments/4718716/foxml_reference_example.xml?version=1&modificationDate=1217861585364
> ),
> > I should be ablo to do something like
> >
> > <foxml:contentLocation REF="changeme:6+DS1+DS1.0"
> >
> >
> > but when I do
> >
> > /var/fedora/client/bin/fedora-
> > ingest.sh f test.xml info:fedora/fedora-system:FOXML-1.1 XXXX:8080 user
> pw
> > http
> >
> > I get Error  : fedora.server.errors.ObjectIntegrityException: FOXML IO
> > stream was bad : Malformed URL: changeme:6+DS1+DS1.0
> >
> > what am I overlooking/doing-wrong ?
> >
> > Thanks in advance
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to