From where did you upload this data? And what kind of meta data are
you talking about?
We've build an import mechanism which fetched files from a WebDAV
server. Each file had additional info (title, description) stored in
the WebDAV repository which had to be imported too. So for importing
from a WebDAV repo I think we might be able to help you.
-will
On 24.09.2009, at 15:27, Benoit Segaert wrote:
I am also very interesting with the import.
I have to upload a lot of documents with multiple metadata into
Magnolia.
Then the zip import is not an option because no metadata will be
imported.
Benoît
-----Original Message-----
From: [email protected] [mailto:user-list-
[email protected]] On Behalf Of Jan Haderka
Sent: mercredi 23 septembre 2009 10:56
To: Magnolia User-List
Subject: Re: [magnolia-user] Importing static content
What are the options for bulk importing data into the DMS while at
the
same time adding the necessary references to the original data nodes?
To do the bulk import, you can zip the images and upload the zipfile.
Magnolia will extract the resources from the zip and also recreate the
folder structure that is in the zip file.
Since this process takes a while (about 30 minutes) and still needs
fine tuning, I would much rather be able to do this through a
stand-alone process (ant task at present). Is it possible to update
the DMS repository directly (while magnolia is shut down) and then
bring it up and have all the content available? Does the DMS expose
Yes, you can update the repo while magnolia is shutdown provided that
the structure and node types used you create will conform with the one
used by Magnolia itself.
any API for performing these types of operations?
You can use beanshell or groovy to script any kind of bulk operations
using all Magnolia API and of course you can also use the API for
importing the documents in DMS.
One option is to store the images as static files within the web app,
but am not sure if they can be managed easily via magnolia (that is
without writing a custom file upload dialog). Another is to learn
the
pattern of the static dms link URL and store them as path references
in the data nodes, and then bulk upload (zip file) all the images
into
the DMS.
the pattern for the links is
http:/<server>:<port>/<contextPath>/dms/<path/to/the/document>/
<filename>.<extension>
Of course you can also store files as a static resources in the web
app,
but then you won't be able to manage them via admin interface anymore.
All that you would be able to do would be to change the link from one
file to another.
HTH,
Jan
I am interested in learning about how other users have dealt with
importing content from other systems into magnolia. Any suggestions
and tips would be most welcome.
Thanks
Rakesh
______________________________________________________________________
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
