On Fri, Jan 23, 2009 at 12:49 AM, Scott Yeadon <[email protected]>wrote:
> Hi Andrew,
>
> Your suggested approach using collections for issues and (sub-)community
> for journals is the approach we took.
Thanks for that. It's nice to know that my idea isn't totally whacky. I am
new to this digital library stuff. Still someone else on this ML thinks that
is not the way to go so I will continue thinking about it. It seems to me
that my approach enables stuff to work out of the box but does not scale
well when the number of journals becomes large. This is because the
societies journal list is expanded in full when the society is displayed.
These lists can take several seconds to build. See my further comments
below.
> For ordering the items within an issue an OAI-ORE aggregation is generated
> by a DSpace journal METS ingestion module.
I don't understand. I'll take a look. It sounds like there is no way out of
the box to make DSpace do the ordering the way I want and that you wound up
with a modified version of DSpace. Is that right? I don't mind the idea of
modifying DSpace, that's the beauty of open source. I have some separate
ideas for modifications myself, which if made, I intend to contribute back.
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.
Are there any plans to send these changes back into the official version of
DSpace? Are the changes done as a general enhancement (as opposed to
something that is very specific to your digital library)?
> The downside to all these different approaches for journal storage in
> DSpace is that Manakin themes can't be shared,
Yes, I realise that. It is not a problem for me as it happens.
Scott.
> > ------------------------------ Message: 3 Date: Thu, 22 Jan 2009
> > 15:35:18 -0600 From: Scott Phillips <[email protected]>
> > 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
>
I am not sure why. Can you explain more please?
> . 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,
>
[snip]
>> > 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.
>
I may have run into this navigation problem already. It seems to me that
DSpace always gives the complete list of sub-communities within a community.
With my approach this list can be rather long and can take several seconds
to build. Is that the problem you are referring to?
>
> >> >
> >> > 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.
>
Thanks for suggesting this. I will have a careful think about it.
>
> >> >
> >> > -Mark
> >> >
> >> > On Jan 22, 2009, at 1:41 AM, Andrew Marlow wrote:
>
> --
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
