<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=027143922-12032004><FONT face=Arial color=#0000ff size=2>Rob
Wolfe writes:</FONT></SPAN></DIV>
<DIV><SPAN class=027143922-12032004>> </SPAN>That being said I think that
SMA, and likely your conference are what is intended as a community.</DIV>
<DIV><SPAN class=027143922-12032004>> </SPAN>Which leaves us to fit the rest
of the hierarchical levels of a community's objects into the one collection
layer. </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=027143922-12032004><FONT face=Arial color=#0000ff size=2>The
capability to create arbitrary hierarchies of communities in DSpace 1.2 (beta
testers testing soon, release circa April?) should go a long way to addressing
this issue. Rob Tansley demonstrated this capability at the DSpace users
group meeting (yesterday!)</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=027143922-12032004><FONT face=Arial color=#0000ff size=2>-
Mick</FONT></SPAN></DIV><!-- Converted from text/plain format --><FONT
face=Arial color=#0000ff size=2></FONT><BR>
<P><FONT size=2>====<BR>Mick Bass<BR><BR>970.898.6788 office
408.216.0584 fax<BR>617.899.3938 mobile 303.494.5202
residence<BR>bass@alum.mit.edu
mick_bass@hp.com<BR>====<BR></FONT></P>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
dspace-general-bounces@mit.edu [mailto:dspace-general-bounces@mit.edu] <B>On
Behalf Of </B>Robert HW Wolfe<BR><B>Sent:</B> Friday, March 12, 2004 3:33
PM<BR><B>To:</B> Petsche, Kevin F; dspace-general@mit.edu<BR><B>Subject:</B>
Re: [Dspace-general] Questions Regarding Structure of
DSpace<BR><BR></FONT></DIV>Kevin,<BR><BR>The Metadata Services Unit in the MIT
libraries recently completed a DSpace submission project for the Singapore-MIT
Alliance (SMA) that encountered the same organizational considerations that
you're working through. SMA wanted to submit articles from conference
proceedings for the past three years. Each conference was organized into
five subject areas. We made each subject area a collection and added
each article to the appropriate collection as an item, capturing metadata at
the level of organization. The years are not architecturally distinct in
this community, but the browse by date feature allows for date-based
organizational views of the material.<BR><BR>I think of the differences
between the files that comprise an item as being trivial. The item is
the conceptually unique object. It doesn't make sense to me let papers
expressing different ides be part of the same item. Practically, search
and discovery of articles that are files just doesn't work. That being
said I think that SMA, and likely your conference are what is intended as a
community. Which leaves us to fit the rest of the hierarchical levels of
a community's objects into the one collection layer. If you can, I
recommend having a look at the SMA collection at MIT's DSpace, <A
href="http://dspace.mit.edu/"
eudora="autourl">http://dspace.mit.edu/</A><BR><BR>Rob Wolfe<BR>Metadata
Specialist<BR>MIT Libraries<BR><BR>At 05:02 PM 3/12/2004 -0500, Petsche, Kevin
F wrote:<BR>
<BLOCKQUOTE class=cite cite="" type="cite">content-class:
urn:content-classes:message<BR>Content-Type:
multipart/alternative;<BR><X-TAB> </X-TAB>boundary="----_=_NextPart_001_01C4087D.B946CA32"<BR><BR><FONT
face=arial size=2>Good day!<BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>Our implementation of
DSpace is currently in beta testing here at IUPUI (<A
href="http://dspace.iupui.edu/">http://dspace.iupui.edu</A>) and we are
getting a great response from some areas of the campus interested in placing
material in the repository. <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>But I am concerned that
I am not setting-up some of these communities and collections in the best
manner. <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>Let me
explain:<BR></FONT><BR><FONT face=arial size=2> <BR></FONT><BR><FONT
face=arial size=2>A few units on campus are wishing to place conference
proceedings for several years into the repository and another
campus-affiliated unit is interested in pursuing the archiving of an
electronic newsletter. The seriality of these projects are causing me
to wonder what the best way to implement these. For example, there s a
unit on campus called the Adult Education Department . The chair of
the department is interested in using DSpace as a repository and archive of
the proceedings for an annual conference that he s very much involved in,
The Midwest Research-to-Practice Conference in Adult, Continuing and
Community Education . It s a two-day conference and makes available
several conference papers each year. <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>Knowing the structure of
IDEA and the relationships among its components (i.e. communities,
collections, items and file), I wonder what the best way to do the above
tasks. <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>My inclination is to
make an Adult Education Department community, with a Midwest
Research-to-Practice Conference collection. This then would seem to
make each year of the conference a separate item, with each paper a separate
file within each item (i.e. year). But this gets to be quite
awkward. Each of these implementers wants to give each contributor the
ability to submit their own paper, but my understanding is that this
requires each contributor to have update authorization which then gives them
the ability to delete papers and change the metadata. Further, if this
is the set-up, I have concerns about the metadata description of each
file. It seems to me that we can add a description.toc field to each
item, but these aren t searchable, are they? Further, like any serial
record, there s only a very general ability to describe the item and not
particular topics that rest within each paper or article. It doesn t
seem very satisfying. <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>The other option that I
ve contemplated is more satisfying. It shifts the structure upwards so
that each paper or article is its own item with accompanying metadata.
But then each conference or online newsletter must be its own community with
each issue being the collection. This, it seems to me, muddles the
repository at the front end, as the list of communities then becomes a
mixture of campus departments, newsletters and conferences. Again,
this seems to be a solution that is not very satisfying.
<BR></FONT><BR><FONT face=arial size=2> <BR></FONT><BR><FONT face=arial
size=2>Can anyone help me to solve my way through this? I ve searched
through the online documentation and DSpace Federation site, but can t seem
to put my finger on the help I need. <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT face=arial size=2>Thanks so much in
advance! <BR></FONT><BR><FONT face=arial
size=2> <BR></FONT><BR><FONT size=4><B>Kevin<BR></B></FONT><BR><FONT
size=4><B> <BR></B></FONT><BR>Kevin Petsche<BR><BR>Assistant
Librarian<BR><BR>Electronic Journals Collection Manager<BR><BR>Digital
Libraries/Cataloging Teams<BR><BR>IUPUI University Library
UL1115D<BR><BR>755 West Michigan Street<BR><BR>Indianapolis, Indiana
46202<BR><BR>317.278.2330<BR><BR>317.278.0368 (fax)<BR><BR><FONT
face="Times New Roman, Times"> <BR></FONT>_______________________________________________<BR>Dspace-general
mailing list<BR>Dspace-general@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/dspace-general"
eudora="autourl">http://mailman.mit.edu/mailman/listinfo/dspace-general</A></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>