<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#000000 size=2>Hi all,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In our project in which we have to implement a DSpace solution, we're actually facing a major problem that might maybe concerns other people working in librairies.</FONT></DIV>
<DIV><FONT face=Arial size=2>We need to submit and preserve periodicals in DSpace in a structuralized form. Example :</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Times magazine</FONT></DIV>
<DIV><FONT face=Arial size=2> |_____________1990</FONT></DIV>
<DIV><FONT face=Arial size=2> |__________jan.pdf</FONT></DIV>
<DIV><FONT face=Arial size=2> |__________feb.pdf</FONT></DIV>
<DIV><FONT face=Arial size=2> |__________...</FONT></DIV>
<DIV><FONT face=Arial size=2> |__________dec.pdf</FONT></DIV>
<DIV><FONT face=Arial size=2> |_____________1991</FONT></DIV>
<DIV><FONT face=Arial size=2> |__________...</FONT></DIV>
<DIV><FONT face=Arial size=2> |_____________...</FONT></DIV>
<DIV><FONT face=Arial size=2> |_____________2006</FONT></DIV>
<DIV><FONT face=Arial size=2> |__________...</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In our library, the main database for metadatas is a catalog. An item can contains a "note" in this catalog and this note possess some descriptive metadatas.</FONT></DIV>
<DIV><FONT face=Arial size=2>In the example above, the Times magazine collection, while containing many pdf items, would possess only 1 note in our catalog. That means, after the transfer from the catalog to DSpace, that the DSpace Collection representing the magazine should be ideally the only object that should contains the metadatas, because we don't want to repeat those metadatas for each of the DSpace Items possessing the pdf files in the whole Collection. This is for performance reason because we have some collections possessing thousands of pdfs (like a newspaper of more than 100 years old and having a pdf for each day).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For our team, that means we are actually considering the solution of making a big change to DSpace so that :</FONT></DIV>
<DIV><FONT face=Arial size=2>1) a collection can have sub-collections (same idea here as Communities);</FONT></DIV>
<DIV><FONT face=Arial size=2>2) a collection can be mapped to the metadatas schema and therefore be considered as an "Item", so that its metadatas would be indexed in the same way. The collection would then be searchable through the dc fields (for example). In that case, if we make a search and it gives one of the item, possessing the pdf, as a result (full-text indexed pdf), we would get the dc metadatas from its "parent" collection, instead having those in the item's record.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>As any people here have the same needs and has begin some works about it? We consider that this can be a very useful add-on for DSpace, resolving almost any kind of digital collections. However, w</FONT><FONT face=Arial size=2>e know that this will not be a simple modification...</FONT></DIV></BODY></HTML>