Hi all,<br> <br>I think it is imposible to build a archival records management system based on DSpace.I am investigating it too.As for my case,I use/customize DSpace as a ebooks warehouse system.My problem is as follows,<br>
<br>(1)How to add more attributes to a item?for example,the price of the ebook,the cover page image of the ebook,the page count of the ebook.<br><br>(2)How to import mass data to the DSpace instead add via workflow book by book?
<br><br>(3)How to produce inventory reports?<br><br>(4)How to customize the authorization system?<br><br>Any idea is appreciated.<br><br>Thank you.<br><br>Best Regards,<br>Anny<br><br>RE: Use of Dspace for managing archival records
<pre>Hi Ernie,<br>><i> We are investigating using DSpace as a respository for institutional<br></i>><i> records. The proposed scope right now includes documents created in the<br><br></i>><i> work of public officials, including MS Office documents, PDF files,
<br></i>><i> graphics, audio and video, (but not e-mail at this time). <br></i>><i><br></i>><i> This seems to differ somewhat from the more common use of DSpace as an<br><br></i>><i> IR in the sense of providing access to pre-prints, dissertations,
<br></i>><i> curriculum materials and other types of documents which are more<br></i>><i> designed for dissemination of information.<br>
</i>><i> <br></i>I think you are conflating file formats (e.g. Word, PDF, MP3, etc.) with <br>genre (pre-prints, articles,<br>datasets, movies, etc.) There are DSpaces with every conceivable type of <br>genre and format...
<br><br>but maybe your point is really to distinguish content that the <br>institution *wants to disseminate*<br>as opposed to what they *want to manage*. Most DSpace sites (including <br>MIT's) are intended<br>for both. The submitters who submit get the dissemination, and the
<br><br>libraries manage that content<br>for them. Some submitters chose *not* to disseminate... they just want <br>their content managed,<br>and the system handles that fine -- it's strictly a local policy <br>decision which you encode in the
<br><br>access rights for the system.<br><br>What DSpace currently lacks for true records management is scheduling... <br>there is a little bit<br>of code in there waiting to be finished and turned on to handle <br>retention schedules and the like,
<br><br>but it isn't current functionality.<br><br>MacKenzie<br><br>-- <br>MacKenzie Smith<br>MIT Libraries</pre><br><br><br><br><br><br><br>