Re: [Dspace-tech] Best Practices for Journal Articles
Hi, you might be interested in the Czech Digital Mathematics Library project. We use DSpace together with Manakin to store and present journals. I'm not sure what do you mean by the articles tied together. You can look at http://dml.cz/ if this is what you want. If you have any question just send me an e-mail. cheers Vlastik Vlastimil Krejčíř Library and Information Centre, Institute of Computer Science Masaryk University in Brno, Czech Republic Email: krejcir (at) ics (dot) muni (dot) cz Phone: +420 549 49 3872 ICQ: 163963217 Jabber: [EMAIL PROTECTED] On Mon, 2 Jun 2008, Thomas A McGee wrote: What's the best methodology for archiving individual articles within an issue of a periodical? 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. _ Tom McGee Seton Hall University TLTC 973 761 9000 x5021 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Best Practices for Journal Articles
Tom What works well for us is to create a separate collection for each issue (the Top-level or Sub-Community will then be the title of the journal, depending on the model you use). Each article is then submitted individually with its own metadata attached. In the end, we create an interactive index page on the Collection home page which lists the articles in that issue. See https://www.up.ac.za/dspace/handle/2263/4136for an example. Kind regards, Ina Ina SmithDigital Research Repository (UPSpace)Manager eApplication SpecialistDepartment of Library ServicesUniversity of Pretoria Pretoria0002South Africa Tel.: +27 12 420 3082Fax: +27 12 362 5100E-mail: [EMAIL PROTECTED]http://www.library.up.ac.za This message and attachments are subject to a disclaimer. Please refer to www.it.up.ac.za/documentation/governance/disclaimer/ for full details. / Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar. On 2008/06/02 at 10:58 PM, in message [EMAIL PROTECTED], Thomas A McGee [EMAIL PROTECTED] wrote: What's the best methodology for archiving individual articles within an issue of a periodical? 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. _Tom McGeeSeton Hall University TLTC973 761 9000 x5021- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Best Practices for Journal Articles
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. Because we weren't wanting to have a separate record for the issue; we just wanted to be able to group articles.. Dorothea -- Dorothea Salo [EMAIL PROTECTED] Digital Repository Librarian AIM: mindsatuw University of Wisconsin Rm 218, Memorial Library (608) 262-5493 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Best Practices for Journal Articles
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 don't have an ETA, but if you're interested, ping me in late July or early August and ask if we have code yet. Dorothea -- Dorothea Salo [EMAIL PROTECTED] Digital Repository Librarian AIM: mindsatuw University of Wisconsin Rm 218, Memorial Library (608) 262-5493 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Best Practices for Journal Articles
What's the best methodology for archiving individual articles within an issue of a periodical? 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. _ Tom McGee Seton Hall University TLTC 973 761 9000 x5021- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Best Practices for Journal Articles
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/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Best Practices for Journal Articles
On Jun 2, 2008, at 8:42 PM, Conal Tuohy wrote: 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 I'm currently working on a strategy to utilize the bibliontology for adding content types to dspace Items (and eventually Colleciton and Bitstreams as well). http://www.bibliontology.com/ The idea would to be able to describe the Bitstreams in an Item or the Items in a collection with bibo terms (classes) such as to capture the type of the Item in a standard way. This includes Articles and Issues. http://wiki.bibliontology.com/index.php/Examples#Article You'll notice the example reuses dc:isPartOf as a means to reference the Journal that Article is part of. (But should be dcterms:isPartOf). I'll excuse the error as this ontology is in a development stage. Introducing a schema with a bibo namespace and terms might be an initial stepping stone to reaching the goal of expressing whole RDF/ OWL Ontologies in DSpace metadata and more specifically, being able to have a clean representation of types. One of my hopes in the future is to actually reuse the RDF representations of dc, dcterms, rdf, rdfs, and bibo as the metadata registry files and see the whole registry be upgraded to be true RDF Schema. Ultimately, this discussion exemplifies some of the requirements we should be documenting and gathering for the 2.0 Data Model work later this year. -Mark ~ Mark R. Diggory - DSpace Developer and Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology Home Page: http://purl.org/net/mdiggory/homepage - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
