Hi Andrew, Your suggested approach using collections for issues and (sub-)community for journals is the approach we took. Unfortunately the hosted journal that intended to go into production didn't eventuate so it isn't implemented in our production repository but there is a screencast (http://www.apsr.edu.au/ore/) and a more recent presentation (http://www.apsr.edu.au/open_access_publishing/yeadon%20ojs-sword.pdf) you can look at which helps illustrate the approach we took. For ordering the items within an issue an OAI-ORE aggregation is generated by a DSpace journal METS ingestion module. We've done a little more work on this late last year, but the above links give you an idea of the process. If you want further info, feel free to contact me off list, as I don't think we've posted the lastest source anywhere.
The downside to all these different approaches for journal storage in DSpace is that Manakin themes can't be shared, but I think to achieve theme sharing beyond simple objects needs some co-ordinated DSpace storage modelling of compound objects and community agreement which is no small task. Good luck! Scott. > ------------------------------ Message: 3 Date: Thu, 22 Jan 2009 > 15:35:18 -0600 From: Scott Phillips <scott.a.phill...@gmail.com> > Subject: Re: [Dspace-tech] How to order the articles within an issue > To: Diggory Mark <mdigg...@gmail.com> Cc: > "dspace-tech@lists.sourceforge.net" > <dspace-tech@lists.sourceforge.net> Message-ID: > <6254f291-71aa-451d-864a-9d18a2505...@gmail.com> Content-Type: > text/plain; charset="us-ascii" You may want to look at a Journal > collection we've done. It doesn't completely address the problem > you're asking about but is in the same sphere, and i second what Mark > said, it is likely best to not use communities and collections in that > manor. http://repositories.tdl.org/tdl/handle/2249.1/5065 Here is the > theme used to generate that view is located here: > http://repositories.tdl.org/tdl/themes/TDL/Periodicals/sitemap.xmap > http://repositories.tdl.org/tdl/themes/TDL/Periodicals/Periodicals.xsl > The trick we used is to add xml describing journal issues in the > metadata of the collection, then the theme knows to interpret this > small bit of data to build a browsable list of journal issues. Each of > those provide links to a masked search page for individual articles, > plus a list to an item that contains the full pdf for the journal. > Here is the current bit of XML on the collection: <issues > xmlns:tdl="http://www.tdl.org/NS/tdl"; xmlns="http://www.tdl.org/NS/tdl > "> <issue vol="66" num="3&4" year="2008" name="" > handle="2249.1/5643"/> <issue vol="66" num="1&2" year="2008" > name="" handle="2249.1/5546"/> <issue vol="65" num="3&4" > year="2007" name="" handle="2249.1/5496"/> <issue vol="65" > num="1&2" year="2007" name="" handle="2249.1/5438"/> <issue > vol="64" num="3&4" year="2006" name="" handle="2249.1/5439"/> > <issue vol="64" num="1&2" year="2006" name="" > handle="2249.1/5440"/> <issue vol="63" num="3&4" year="2005" > name="" handle="2249.1/5441"/> <issue vol="63" num="1&2" > year="2005" name="" handle="2249.1/5442"/> <issue vol="62" > num="3&4" year="2004" name="" handle="2249.1/5443"/> <issue > vol="62" num="1&2" year="2004" name="" handle="2249.1/5444"/> > <issue vol="61" num="3&4" year="2003" name="" > handle="2249.1/5445"/> <issue vol="61" num="1&2" year="2003" > name="" handle="2249.1/5446"/> <issue vol="60" num="3&4" > year="2002" name="" handle="2249.1/5447"/> <issue vol="60" > num="1&2" year="2002" name="" handle="2249.1/5448"/> </issues> > Scott-- On Jan 22, 2009, at 2:08 PM, Diggory Mark wrote: >> > Andrew, >> > >> > I might recommend avoiding using Collections for Issues, mostly >> > because then your going to end up with "lots" of the them, and that >> > tends to make the interface both difficult to navigate and maintain. >> > >> > Another possibility to consider, instead, add the issue detail >> > either to the Item directly, or possibly create separate Items to >> > hold the issue metadata (relating them to one another in >> > dc.relation.isPartOf/hasPart fields). >> > >> > Thus: >> > >> > Society = Community >> > >> > Journal = Collection >> > >> > Issue and its Errata: Held in "Issue Item" >> > >> > Article and its Errata: Held in "Article Item" >> > >> > You might then customize your presentation and search to Group >> > Articles under Issues. >> > >> > -Mark >> > >> > On Jan 22, 2009, at 1:41 AM, Andrew Marlow wrote: >> > >> >>> >> I am trying to set up a DSpace that models societies, journals, >>> >> issues and articles. Each article is an item. The collection that >>> >> contains the items is an issue. The journal that publishes the >>> >> issue(s) is a sub-community, and the society that publishes the >>> >> journal(s) is a community. My question is, how do I make it so that >>> >> the collection orders the items the way I want? An issue has a >>> >> particular order for the articles because it relates to the >>> >> physical printed version. That's the order I want for the >>> >> collection also. I think collections are ordered by publish date >>> >> (please correct me if I'm wrong about that). That's not good enough >>> >> for me since an issue has a single publish date but many articles. >>> >> This makes the publish date for all the collection's items the same. >>> >> -- >>> >> Regards, >>> >> >>> >> Andrew M. >>> >> http://www.andrewpetermarlow.co.uk >>> >> >>> >> ------------------------------------------------------------------------------ >>> >> This SF.net email is sponsored by: >>> >> SourcForge Community >>> >> SourceForge wants to tell your story. >>> >> http://p.sf.net/sfu/sf-spreadtheword_______________________________________________ >>> >> DSpace-tech mailing list >>> >> DSpace-tech@lists.sourceforge.net >>> >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >>> >> > >> > ~~~~~~~~~~~~~ >> > Mark R. Diggory >> > http://purl.org/net/mdiggory/homepage >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > This SF.net email is sponsored by: >> > SourcForge Community >> > SourceForge wants to tell your story. >> > http://p.sf.net/sfu/sf-spreadtheword_______________________________________________ >> > DSpace-tech mailing list >> > DSpace-tech@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/dspace-tech >> > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > > ------------------------------ > > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > End of DSpace-tech Digest, Vol 33, Issue 50 > ******************************************* > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
