On Mon, 2008-06-02 at 16:04 -0500, Dorothea Salo wrote: > On Mon, Jun 2, 2008 at 3:58 PM, Thomas A McGee <[EMAIL PROTECTED]> wrote: > > > What's the best methodology for archiving individual articles within an > > issue of a periodical? > > I don't think there's one answer to this. Partly it depends on the > journal's production workflow and what they're willing to give you. > I'm not a big fan of archiving whole issues in a single item, but > sometimes that's how I get 'em. Such is life. > > We'd like to have the metadata be more closely tied > > to an individual author's work, as well as let users more easily find the > > section they need. But we'd also like to keep the articles tied together as > > part of a master entry which represents the entire issue. > > We're looking at this where we are too. I suspect the way we're going > to go is to write a small Manakin Aspect that groups items based on > dumb string-matching in a specific Dublin Core field (probably > relation.ispartof). There's almost certainly a better way, but we > think this should be reasonably feasible and effective.
I think DC.Relation.isPartOf (and the inverse relation DC.Relation.hasPart) is a good idea, but why would you use "dumb string-matching"? Why not use the (handle) URI of the items? e.g. the DSpace item representing the issue would have dc.relation.haspart fields each equal to the handle of an article, and each article could have an ispartof field equal to the handle of the issue record. Con -- Conal Tuohy New Zealand Electronic Text Centre www.nzetc.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
