Re: [Dspace-tech] Metadata advice
[rant] In general I think that one should not extend the 'dc' namespace which ships with DSpace, but follow a procedure like this: 1) look around for one or more suitable schemas which already define the attributes you wish to represent. If you find them, use them. DSpace supports well any reasonable number of schemas (so long as they can be mapped to a 1- or 2-level hierarchy). 2) create one or more local namespaces to hold any attributes which are unique to your collection(s). Document these thoroughly, as if you were a standards body. Consider whether your requirements are really unique or only generally unmet -- you might wish to offer your work for others to use and extend. One should always try to use existing schemas if this is practical, because their terms have agreed-upon meaning. Consider: if information on your holdings is harvested by another site, how will the harvester understand the attributes you have added? If you must create new namespaces, publish your specifications so that others will be able to understand and use them. [end rant] There has been some discussion of making DSpace's 'dc' schema immutable for just such reasons, and of shipping additional widely-used schemas (not yet identified) with the product. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. smime.p7s Description: S/MIME cryptographic signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] DSpace won't send any notification email...
Hi, Our DSpace instances suddenly stop sending notification email to anyone, including those authorized for approving, edit metadata... I have checked in the mail.log and could not find any email sent out from the system. Could anyone please point me where I should check to fix the system? Thank you in advance. Panyarak Ngamsritragul Prince of Songkla University. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Change some text in messages.xml - in what directory? And how to make the changes appear?
Hello everyone, I want to change some text in messages.xml - in what directory should I do this? And how do I make the changes appear? Do I need to rebuild DSpace? Thank you! /mango_pango -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Metadata advice
Srijan, What a great project! Your approach is a sensible one. However, you'll quickly encounter that Dspace does little to support the mapping between the two Item types and you will endup starting to consider altering the item search and browse indexing among other parts of the system that don't do too well with "relationships" between Items. To compensate for this I recommend a twofold approach 1.) Do start to create "Album" Items, workout a set of metadata fields that you feel are relevant for Albums such that you can capture all the metadata about the album into one record and manage it there. 2.) In the short term, also "replicate" some of the relevant metadata you want to be able to search and browse on for a specific song into the Song Item metadata record. This will allow you to create browse indexes for your songs that will return all songs based on name of the album or the album author. Eventually DSpace will get smarter about managing rendering relationships. We have a project in GSoC that looks to include Semantic Authority Control into DSpace and that would be capable of supporting the lookup up existing "Album type" Items for linking to when submitting a song into DSpace. https://wiki.duraspace.org/display/GSOC/GSoC+2011+-+DSpace+SKOS+Authority+Controls There were a few presentations at OR that explored how to customize DSpace to support relationships between Items. Kim Shepard and Stuart Lewis worked out some ideas for an archive of Maori Tribal Songs / Music. I would highly recommend chatting with them about their approach which will allow you to create views over the Album and its Related Songs by querying Solr to join those results. Best Regards, Mark On Wed, Jun 8, 2011 at 11:51 PM, Srijan Deshpande wrote: > Hello, > I'm setting up a DSpace repository for our archive of Indian Classical > Music. I'm currently working on our metadata schema and I have some > questions and difficulties I need help with. > One of my basic requirements is that each song be treated as an item in > DSpace. This is because a 'song' (a composition) is the basic tangible unit > in this music - compositions are taught, studied, written down, exchanged, > and performed. Invariably, a single traditional composition will have a > number of different versions, performed by a number of artists. Students of > music, therefore, will want to search for a traditional composition and will > expect to find a number of versions of it. > In this situation, I need to know how to represent albums, or recordings of > live concerts, both of which contain a number of compositions. From my > research (I'm no metadata expert), this is what I've come up with: > > I create a separate item in DSpace for each song in the album > I also create an item for the album > In the album-item, I use the dc.relation.haspart property to enter URIs of > each song-item > In each song-item, I use the dc.relation.ispartof property to enter the URI > of the album to which the song belongs > > Does this sound right? > We also have handwritten musical scores (notation) of many compositions. Is > it correct to use the dc.relation.isformatof property to indicate a > relationship between an recorded composition (audio file) and its musical > notation (scanned image)? I'd have to use the dc.relation.isformatof > property on both items right? > --- > Indian music is based on melodic frameworks called 'raagas'. Any composition > in Indian Classical music is derived from one of the hundreds of raagas. > Therefore the raaga is an important characteristic of any composition. Would > it be appropriate to indicate this using a new qualifier for the dc.subject > property? As in dc.subject.raaga? > Similarly the various rhythms to which the compositions are sung are called > taalas. Consequently, I should use dc.subject.tala, correct? Also in this > case, I don't see myself using dc.subject without any qualifiers at all. Is > that appropriate? > --- > The compositions are classified into a number of sub-genres named 'khayal', > 'thumri', 'bhajan' and so on. Which would be more appropriate here: > dc.coverage.genre or dc.subject.genre? Often, there are also sub-genres, so > dc.coverage.subgenre? > > And one of my biggest problems is: Any performance will have a number of > artists performing together - a singer, supporting vocalists, > instrumentalists, percussionists etc. I can list these using dc.contributor > with marcrel qualifiers, such as dc.contributor.singer, > dc.contributor.instrumentalist etc. But how do I indicate each contributor's > role? How do I show which of the contributors is the singer, which is the > percussionist and so on? > --- > For the languages of the compositions, most are in Dialects of the Hindi > language. There is a standard language code for Hindi, but there are no > codes for dialects of hindi. How should I represent these dialects? Or > should I stick to just showing 'Hindi' as the language of the composition? > --
Re: [Dspace-tech] Metadata advice
Typo on Kim's email, it should have been On Mon, Jun 13, 2011 at 1:44 PM, Mark Diggory wrote: > Srijan, > > What a great project! > > Your approach is a sensible one. However, you'll quickly encounter > that Dspace does little to support the mapping between the two Item > types and you will endup starting to consider altering the item search > and browse indexing among other parts of the system that don't do too > well with "relationships" between Items. To compensate for this I > recommend a twofold approach > > 1.) Do start to create "Album" Items, workout a set of metadata fields > that you feel are relevant for Albums such that you can capture all > the metadata about the album into one record and manage it there. > > 2.) In the short term, also "replicate" some of the relevant metadata > you want to be able to search and browse on for a specific song into > the Song Item metadata record. This will allow you to create browse > indexes for your songs that will return all songs based on name of the > album or the album author. > > Eventually DSpace will get smarter about managing rendering > relationships. We have a project in GSoC that looks to include > Semantic Authority Control into DSpace and that would be capable of > supporting the lookup up existing "Album type" Items for linking to > when submitting a song into DSpace. > https://wiki.duraspace.org/display/GSOC/GSoC+2011+-+DSpace+SKOS+Authority+Controls > > There were a few presentations at OR that explored how to customize > DSpace to support relationships between Items. Kim Shepard and Stuart > Lewis worked out some ideas for an archive of Maori Tribal Songs / > Music. I would highly recommend chatting with them about their > approach which will allow you to create views over the Album and its > Related Songs by querying Solr to join those results. > > Best Regards, > Mark > > > On Wed, Jun 8, 2011 at 11:51 PM, Srijan Deshpande wrote: >> Hello, >> I'm setting up a DSpace repository for our archive of Indian Classical >> Music. I'm currently working on our metadata schema and I have some >> questions and difficulties I need help with. >> One of my basic requirements is that each song be treated as an item in >> DSpace. This is because a 'song' (a composition) is the basic tangible unit >> in this music - compositions are taught, studied, written down, exchanged, >> and performed. Invariably, a single traditional composition will have a >> number of different versions, performed by a number of artists. Students of >> music, therefore, will want to search for a traditional composition and will >> expect to find a number of versions of it. >> In this situation, I need to know how to represent albums, or recordings of >> live concerts, both of which contain a number of compositions. From my >> research (I'm no metadata expert), this is what I've come up with: >> >> I create a separate item in DSpace for each song in the album >> I also create an item for the album >> In the album-item, I use the dc.relation.haspart property to enter URIs of >> each song-item >> In each song-item, I use the dc.relation.ispartof property to enter the URI >> of the album to which the song belongs >> >> Does this sound right? >> We also have handwritten musical scores (notation) of many compositions. Is >> it correct to use the dc.relation.isformatof property to indicate a >> relationship between an recorded composition (audio file) and its musical >> notation (scanned image)? I'd have to use the dc.relation.isformatof >> property on both items right? >> --- >> Indian music is based on melodic frameworks called 'raagas'. Any composition >> in Indian Classical music is derived from one of the hundreds of raagas. >> Therefore the raaga is an important characteristic of any composition. Would >> it be appropriate to indicate this using a new qualifier for the dc.subject >> property? As in dc.subject.raaga? >> Similarly the various rhythms to which the compositions are sung are called >> taalas. Consequently, I should use dc.subject.tala, correct? Also in this >> case, I don't see myself using dc.subject without any qualifiers at all. Is >> that appropriate? >> --- >> The compositions are classified into a number of sub-genres named 'khayal', >> 'thumri', 'bhajan' and so on. Which would be more appropriate here: >> dc.coverage.genre or dc.subject.genre? Often, there are also sub-genres, so >> dc.coverage.subgenre? >> >> And one of my biggest problems is: Any performance will have a number of >> artists performing together - a singer, supporting vocalists, >> instrumentalists, percussionists etc. I can list these using dc.contributor >> with marcrel qualifiers, such as dc.contributor.singer, >> dc.contributor.instrumentalist etc. But how do I indicate each contributor's >> role? How do I show which of the contributors is the singer, which is the >> percussionist and so on? >> --- >> For the languages of the compositions, most are in Dialects of the Hindi >> langu
Re: [Dspace-tech] Change some text in messages.xml - in what directory? And how to make the changes appear?
I find the messages.xml file in my 1.7.1 installation at: /dspace/webapps/xmlui/i18n/messages.xml The command> locate messages.xmlfound 7 instances in the "src-release" directory-tree but only the instance above in the actual dspace installation. Hope that helps, -DA On 6/13/2011 1:12 PM, Magnus Norberg wrote: Hello everyone, I want to change some text in messages.xml - in what directory should I do this? And how do I make the changes appear? Do I need to rebuild DSpace? Thank you! /mango_pango -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] dspace login link
We have both the PasswordAuthentication and LDAPHierarchicalAuthentication enabled, however I only want users to be able to sign in from the LDAPHierarchicalAuthentication and use the Password Authentication as a fall back for a administrators account. I was wondering if I can only display the login for LDAPHierarchicalAuthentication, or should I disable the Password Authentication and only enable it when I need to use the Administrators account? What have other institutions done? -Phil - Philip Shafer Web Developer Rowan Univeristy Library Services Ph: 856-256-4418 E-mail: sha...@rowan.edu -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Change some text in messages.xml - in what directory? And how to make the changes appear?
Oops, I forgot to mention the importance of running updatedb to populate the database that locate depends on to find files. See for example: http://www.go2linux.org/find_locate_files_on_linux -DA I find the messages.xml file in my 1.7.1 installation at: /dspace/webapps/xmlui/i18n/messages.xml The command: locate messages.xml found 7 instances in the "src-release" directory-tree but only the instance above in the actual dspace installation. Hope that helps, -DA On 6/13/2011 1:12 PM, Magnus Norberg wrote: Hello everyone, I want to change some text in messages.xml - in what directory should I do this? And how do I make the changes appear? Do I need to rebuild DSpace? Thank you! /mango_pango -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Error pages in DSpace 1.7.1
Some time ago, I had to make a change to the DSpace error pages in version 1.5.1 in order to get any error besides the “Internal Server error” to display. I had to comment this line out in all of the objects under /error in webapps: <%@ page isErrorPage="true" %> I am in the process of implementing version 1.7.1 and I see this still has not been corrected and thought I’d mention it. Sue Sue Walker-Thornton Software Developer/Database Administrator NASA Langley Research Center|LITES Contract SGT, Inc.|130 Research Drive Hampton, Va. 23666 Office: (757) 224-4074 Mobile: (757) 506-9903 Fax: (757) 224-4001 susan.m.thorn...@nasa.gov -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Metadata advice
Dear Mark, Thanks! Yes this is quite a project and a very challenging one at that! Will I really have to modify the search and browse indexing extensively? The way I had imagined this would work was: I would make relation.haspart (for the album-items) and relation.ispartof (for the song items) indexable and that would be it - that would pretty much serve my purpose, right? So if a user comes across a song that is part of an album, that fact would be shown to him (I'd have to customize the way the relation.ispartof field is displayed) and he'd be able to visit the album's page (since the value of the relation.ispartof field could be the URI of the album). Also, vice versa, if the user visits an album's listing, each of the component tracks could be listed using relation.haspart - the values of which would be the individual songs' URIs. This should work, right? The SKoS authority control looks fantastic and I can imagine how incredibly useful it would be for a project like ours! Looking forward to it. I've actually spoken to Kim Shepherd about his work and he has promised to send me some stuff describing his ideas, which I'm really looking forward to. Thanks again! -Srijan -- Srijan Deshpande http://be.net/ontheweb Sent with Sparrow (http://www.sparrowmailapp.com) On Tuesday 14 June 2011 at 12:15 AM, Mark Diggory wrote: > Typo on Kim's email, it should have been > > On Mon, Jun 13, 2011 at 1:44 PM, Mark Diggory (mailto:mdigg...@atmire.com)> wrote: > > Srijan, > > > > What a great project! > > > > Your approach is a sensible one. However, you'll quickly encounter > > that Dspace does little to support the mapping between the two Item > > types and you will endup starting to consider altering the item search > > and browse indexing among other parts of the system that don't do too > > well with "relationships" between Items. To compensate for this I > > recommend a twofold approach > > > > 1.) Do start to create "Album" Items, workout a set of metadata fields > > that you feel are relevant for Albums such that you can capture all > > the metadata about the album into one record and manage it there. > > > > 2.) In the short term, also "replicate" some of the relevant metadata > > you want to be able to search and browse on for a specific song into > > the Song Item metadata record. This will allow you to create browse > > indexes for your songs that will return all songs based on name of the > > album or the album author. > > > > Eventually DSpace will get smarter about managing rendering > > relationships. We have a project in GSoC that looks to include > > Semantic Authority Control into DSpace and that would be capable of > > supporting the lookup up existing "Album type" Items for linking to > > when submitting a song into DSpace. > > https://wiki.duraspace.org/display/GSOC/GSoC+2011+-+DSpace+SKOS+Authority+Controls > > > > There were a few presentations at OR that explored how to customize > > DSpace to support relationships between Items. Kim Shepard and Stuart > > Lewis worked out some ideas for an archive of Maori Tribal Songs / > > Music. I would highly recommend chatting with them about their > > approach which will allow you to create views over the Album and its > > Related Songs by querying Solr to join those results. > > > > Best Regards, > > Mark > > > > > > On Wed, Jun 8, 2011 at 11:51 PM, Srijan Deshpande > (mailto:srij...@gmail.com)> wrote: > > > Hello, > > > I'm setting up a DSpace repository for our archive of Indian Classical > > > Music. I'm currently working on our metadata schema and I have some > > > questions and difficulties I need help with. > > > One of my basic requirements is that each song be treated as an item in > > > DSpace. This is because a 'song' (a composition) is the basic tangible > > > unit > > > in this music - compositions are taught, studied, written down, exchanged, > > > and performed. Invariably, a single traditional composition will have a > > > number of different versions, performed by a number of artists. Students > > > of > > > music, therefore, will want to search for a traditional composition and > > > will > > > expect to find a number of versions of it. > > > In this situation, I need to know how to represent albums, or recordings > > > of > > > live concerts, both of which contain a number of compositions. From my > > > research (I'm no metadata expert), this is what I've come up with: > > > > > > I create a separate item in DSpace for each song in the album > > > I also create an item for the album > > > In the album-item, I use the dc.relation.haspart property to enter URIs of > > > each song-item > > > In each song-item, I use the dc.relation.ispartof property to enter the > > > URI > > > of the album to which the song belongs > > > > > > Does this sound right? > > > We also have handwritten musical scores (notation) of many compositions. > > > Is > > > it correct to use the dc.relation.isformatof propert
Re: [Dspace-tech] Metadata advice
Thanks for that! I'm looking around for schemas that I could base mine on, but there are a bunch of terms crucial to this repository that are specific to Indian Music and although I had hoped there might be a schema that incorporates them, there really doesn't seem to be (I've searched high and low!) I don intend to create a local namespace, although I hadn't considered documenting it thoroughly like you recommend. I will now! I also ought to make the documentation public somewhere, right? On our repository's public website perhaps? Thanks! -Srijan On Monday 13 June 2011 at 7:03 PM, Mark H. Wood wrote: > [rant] > > In general I think that one should not extend the 'dc' namespace which > ships with DSpace, but follow a procedure like this: > > 1) look around for one or more suitable schemas which already define > the attributes you wish to represent. If you find them, use > them. DSpace supports well any reasonable number of schemas (so > long as they can be mapped to a 1- or 2-level hierarchy). > > 2) create one or more local namespaces to hold any attributes which > are unique to your collection(s). Document these thoroughly, as > if you were a standards body. Consider whether your requirements > are really unique or only generally unmet -- you might wish to > offer your work for others to use and extend. > > One should always try to use existing schemas if this is practical, > because their terms have agreed-upon meaning. Consider: if > information on your holdings is harvested by another site, how will > the harvester understand the attributes you have added? > > If you must create new namespaces, publish your specifications so that > others will be able to understand and use them. > > [end rant] > > There has been some discussion of making DSpace's 'dc' schema > immutable for just such reasons, and of shipping additional > widely-used schemas (not yet identified) with the product. > > -- > Mark H. Wood, Lead System Programmer mw...@iupui.edu (mailto:mw...@iupui.edu) > Asking whether markets are efficient is like asking whether people are smart. > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net (mailto:DSpace-tech@lists.sourceforge.net) > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > Attachments: > - smime.p7s > -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
