Dear Nicolas,

Thanks so much for the detailed reply, but this isn't working for me!
As you said, there was no Messages.properties file in the dspace source
folder, so I downloaded it from
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/resources/Messages.properties(Since
I couldn't find an english version at the link suggested by you).

I then added messages such as itemlist.hmo.title = Title and
metadata.hmo.title = Title. I then saved the file in dspace-3.1-
release/dspace/modules/jspui/src/main/resources/. (There was no 'resources'
folder inside the 'main' folder, so I created it and put the
Messages.properties file in there.)

I then ran mvn package and ant update, restarted tomcat and tried again,
but I still see ???itemlist.hmo.title???.

Is there anything else that might be wrong?

Thanks Again!
Srijan


On 5 April 2013 19:31, Nicolás Rucks <[email protected]> wrote:

> Hi Srijan,
>
> This is right for version 1.8.2, so I'm not sure if it's useful for other
> versions, but I guess it is.
>
> A) WHICH FILE
> Most of the "Messages" shown on the front end come from a file named
> "Messages.properties"
> or
> "Messages_xx.properties" where "xx" is a language code (for example
> "Messages_es.properties" for Spanish, "Messages_de.properties" for German).
> You need one for each language you support.
>
> B) WHERE DOES THE FILE COME FROM
> The problem is (or at least it was MY problem), that these files do not
> come by default; I had to download them from
>
> https://svn.duraspace.org/dspace/modules/dspace-api-lang/tags/dspace-api-lang-1.8.0.3/src/main/resources/
>
> C) WHAT TO CHANGE IN THE FILE
> . In the Messages.properties you will find all the messages defined, like
> browse.page-title            = Browsing DSpace
> browse.et-al                 = et al
> browse.type.metadata.author  = Author
> browse.type.metadata.subject = Subject
> browse.type.item.title       = Title
> browse.type.item.dateissued  = Issue Date
> browse.type.item.dateaccessioned = Submit Date
> itemlist.dc.date.issued        = Issue Date
> itemlist.dc.title              = Title
>
> etc.
>
> So you will have to modify the file and include there all the new metadata
> fields you have defined, each in a new line. For example:
> itemlist.hmo.title = Srijan style title
> You will probably need to define the message for the individual record
> display:
> metadata.hmo.title = Srijan style title
>
> Anyway, whenever you see something like ???itemlist.hmo.title??? , it
> means you have to define that parameter in the Message.properties file.
>
>
> D) WHERE DOES THE FILE GO TO
> In production path, the files live in this directory (supposing the dspace
> root path is /dspace/ )
> /dspace/webapps/jspui/WEB-INF/classes/
> So I have for instance these two files, in order to support both english
> and spanish languages:
> /dspace/webapps/jspui/WEB-INF/classes/Messages.properties
> /dspace/webapps/jspui/WEB-INF/classes/Messages_es.properties
>
> But since you will have to execute "maven" and "ant", you will have to put
> the Messages.properties or Messages_xx.properties in the SOURCE path:
>
> [your
> path]/dspace-1.8.2-src-release/dspace/modules/jspui/src/main/resources/
>
> At least it works for me.
>
>
> E) BONUS TRACK :)
> Now, regarding the link to the individual item's record,
> as far as my experience goes, the only metadata that links to the
> individual item is dc.title!
> And that is hardcoded in the java programs!!!
> No mention in the manual, no information from the list, no parameter
> available to change.
> (Somebody please prove me wrong!)
> So far, I have identified these two files
>
> [path]/dspace-1.8.2-src-release/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/jsptag/BrowseListTag.java
>
> [path]/dspace-1.8.2-src-release/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/jsptag/ItemListTag.java
>
> Line 490 of BrowseListTag.java :
>         // format the title field correctly (as long as the item isn't
> withdrawn, link to it)
>         else if (field.equals(titleField))
>         {
>                 metadata = "<a href=\"" + hrq.getContextPath() + "/handle/"
>                 + items[i].getHandle() + "\">"
>                 + Utils.addEntities(metadataArray[0].value)
>                 + "</a>";
>         }
>
> I guess I have the same problem as you do, for using a custom metadata
> schema.
> So you will have to KEEP using the dc.title field in order to link to the
> individual item.
> Or find a workaround in the java files. I didn't go so far as modifying
> the programs, but it guess it should be possible to modify it. Although
> quite a "get you hands dirty" solution...
> It would be a most useful feature to be able to define metadatas that lead
> to the individual item...
> At least for me and you.
> I wonder if that feature would be useful to anybody else.
>
> I sincerely hope this is useful to you.
>
> Saludos,
> Nicolas Rucks
> Argentina
>
> ________________________________
> > De: Srijan Deshpande [mailto:[email protected]]
> > Enviado el: viernes 05 de abril de 2013 02:56
> > Para: [email protected]
> > Asunto: [Dspace-tech] JSPUI search results problem - help please!
> >
> >
> > Hello,
> >
> > Posting this again because there seems to be a problem with the one I
> sent a few days ago:
> > I just configured webui.itemlist.columns in dspace.cfg to include
> elements from my custom metadata schema in JSPUI's item list display.
> >
> > This worked, but as can be seen in the included screenshot, the column
> titles show ???itemlist.hmo.title??? or ???itemlist.hmo.subject.*???
> instead of simply 'Title' or 'Subject'. (my custom metadata schema is named
> 'hmo')
> >
> > How do I change this?
> >
> > Also, please notice that none of the search results are links that can
> take me to the individual item's  record.
> >
> > Help please!
> > Thanks,
> > Srijan
> >
>
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to