Dear Don,<br><br>Thank you very very much. I hadn't picked up on the Item Importer when perusing through the documentation previously and after a quick scan of it along with your helpful email, I think that will get me started on the right track.
<br><br>As for the kind of item that I want to import, it doesn't have a name yet but for now let's call it a "bundle of web page resources" or a "bundle" for short. The files comprising this "bundle" are a logically related collection of files (images such as in PNG format, unstructured UTF-8 encoded text files, XHTML files and CSS style sheet files, etc.). When I looked at that very nice diagram (the PDF depicting the DSpace system), the diagram said verbatim:
<br><br><blockquote>An item is an "archival atom" consisting of grouped, related content and associated descriptions (metadata). <br></blockquote>Unless I have misinterpreted, the DSpace definition of an item seems appropriate to my "bundle" situation. It does look as if, however, that Dublin Core will be required for each file in this "bundle" item. I was hoping that I could use one DC metadata file to describe the "bundle" as a whole and not necessarily worry about the metadata description of each file or part of the "bundle" but I can see how that would be too limiting and the option needs to exist to describe each and every file in an item if need be.
<br><br>Thanks again for pointing me in the right direction. Most likely the Importer will be fine to start with and I'll have to do some additional investigating per your suggestions such as with regard to handling the item structure.
<br><br>Cheers,<br><br>-Sergio <br><br><div><span class="gmail_quote">On 5/3/06, <b class="gmail_sendername">Don Gourley</b> <<a href="mailto:gourley@wrlc.org">gourley@wrlc.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sergio,<br><br>I don't quite understand what kind of item you want to import into<br>DSpace...and if it is just one big item I'm not sure what value<br>DSpace would offer to managing it. But in general for importing<br>items you would use the ItemImport program:
<br><br><a href="http://www.dspace.org/technology/system-docs/application.html#itemimporter">http://www.dspace.org/technology/system-docs/application.html#itemimporter</a><br><br>This program reads the DSpace "simple archive format" which is a
<br>directory structure with folders for each item which contain a<br>very simple XML encoding of Dublin Core, the content files and<br>a file listing the content files. I have written Perl scripts<br>to create this directory structure and it is pretty easy.
<br><br>I think the content files can be structured in sub-folders but<br>I've never tried that and don't know how (or if) that structure<br>would be translated into DSpace's item structure. The way I've<br>dealt with structural relationships between files in an item is
<br>by including another file in each item which includes structural<br>metadata. Another option in your case might be to use DSpace's<br>community/sub-community/collection/item hierarchy to map your<br>directories and files to multiple items instead of a single one.
<br><br>In 1.4 you have another option which is to create a packager<br>plugin to ingest your item into DSpace. However, the plugin<br>must be written in Java...I don't think there is any easy way<br>to use a scripting language.
<br><br>-Don<br><br>On Wed, May 3, 2006 9:26 am, Sergio Trejo wrote:<br>> Hello All,<br>><br>> I am about to install DSpace 1.4 alpha. I will gladly test it out and be<br>> happy to provide feedback to the maintainers. I had started to look at
<br>> DSpace last year but was called to do work on a different project. Now I am<br>> returning to DSpace and I am looking forward to it!.<br>><br>> I have a simple use case:<br>><br>> * I have, on the file system of the server which I plan to install DSpace
<br>> (Mac OS X Server), a top-level directory. This top-level directory contains<br>> files, sub-directories, and a few symbolic links (the links are to other<br>> directories within the top-level directory). The files contained in this
<br>> directory structure on the file system are comprised mostly of web-related<br>> content (images in JPG and PNG), text, CSS, XHTML, etc. I also have one and<br>> only one RDF file for the entire top-level directory which contains Simple
<br>> Dublin Core (15 elements maximum) that describe the entire directory of the<br>> content I just mentioned (DC: author, date, identifier, publisher, etc.).<br>><br>> * I want to turn the above-described directory (and all of its content and
<br>> RDF metdata file and sub-directories) as a DSpace "item" (a DSpace archival<br>> atom) as per the gorgeous diagram found at<br>> <a href="http://www.dspace.org/introduction/dspace-diagram.pdf">http://www.dspace.org/introduction/dspace-diagram.pdf
</a><br>><br>> * I would like to write a shell script that may be run on the Mac OS X<br>> Server machine that is also hosting the DSpace 1.4 alpha system, which<br>> script would be run by a designated Collection Curator and used to
<br>> importthe above-mentioned DSpace item. I would thus like to avoid or<br>> highly<br>> minimize the requirement for a person (curator) to use the DSpace Web<br>> Interface and to avoid the need to fill out web forms for manually entering
<br>> metadata about the "item". The motto I must take in my small and lean<br>> organization is borrowed from the Ruby on Rails community which espouses<br>> simplicity and agile approaches: DRY (Don't Repeat Yourself) <
<br>> <a href="http://wiki.rubyonrails.com/rails/pages/DRY">http://wiki.rubyonrails.com/rails/pages/DRY</a> ><br>><br>> Looking at the DSpace documentation, it is my understanding that in order to<br>> import an "item" into a DSpace repository, I will need to somehow create a
<br>> SIP (Submission Information Package) file. A SIP apparently is "an XML<br>> metadata document with some content files" but I am having a hard time<br>> finding detailed documentation on how to create a SIP and just what goes
<br>> into this "XML metadata document" as well as what "content files" are<br>> required.<br>><br>> Could my proposed shell shell script, for example, parse the Simple Dublin<br>> Core contained in the RDF document that both describes the and is a part of
<br>> the item, to generate a machine-meaningful SIP? How complex of a process<br>> might this be, to create a SIP? Will I need more than Simple Dublin Core to<br>> achieve all of this? Has anyone done something similar? My goal is to try
<br>> and keep things as easy on people as possible. It is my job to make other<br>> people's lives as easy as possible ... I am fluent in scripting languages<br>> (python works great as does ruby) and am looking forward to creating SIPs
<br>> for items.<br>><br>> Thank you for any suggestions.<br>><br>> -Sergio<br>> _______________________________________________<br>> Dspace-general mailing list<br>> <a href="mailto:Dspace-general@mit.edu">
Dspace-general@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/dspace-general">http://mailman.mit.edu/mailman/listinfo/dspace-general</a><br>><br><br><br></blockquote></div><br>