|
From: Demian K. <dem...@vi...> - 2016-01-21 21:01:42
|
Where do you want the abstract to display? Where are you storing it in the Solr index? Depending on the answers, you may either be able to address this through indexing, record driver changes or template changes. The idea of locale-specific fields is an interesting one. It could certainly be done relatively easily, in the sense that you can figure out the current locale from any template or from any piece of VuFind code that has the translator injected into it (and adding an injected translator is trivial). The harder part is figuring out an overall strategy for handling this. It’s easy enough to add this as a special case for one field, but perhaps it would be useful to create a more generic mechanism that works across many fields. Anyway, I can provide more specifics if you are interested. As far as VuFind’s to-do list goes, you might find it helpful to look at the “Wishlist” in JIRA: https://vufind.org/jira/browse/VUFIND/fixforversion/10011/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel This is where we keep all tickets that are not associated with a specific version. It’s quite possible there are some strange/obsolete ideas in there, but there may also be some inspirational ones. Certainly the idea of integrated social media comments is addressed by one of the existing tickets – that’s not something that was ever a core feature, though a demo was put together long ago as a patch for VuFind 1.x; the challenge there is figuring out the best mechanism for integration. Probably a custom RecordTab class would make the most sense at this point! Anyway, thanks for your interest in helping, and sorry if my answers to your abstract questions are overly vague – I’m a little short on time just now, but will happily elaborate tomorrow if you need more details; just let me know! - Demian From: SamuelOPH [mailto:sam...@gm...] Sent: Thursday, January 21, 2016 1:51 PM To: vuf...@li... Subject: [VuFind-General] Show description.resumo (instead of abstract) Hi all, I would like to check with somebody before attempting any changes. We have a lot of records from Dspace that has two DC fields: * dc.description.abstract * dc.description.resumo *"resumo" means abstract in portuguese-br. So far so good, VuFind harvest both fields flawlessly and the resumo appears when there's no abstract, the problem is that resumo only shows at "staff view". I think the ideal fix would be to show the portuguese abstract when the locale is set to pt-br, and the english one on the other cases, but I know such a change is not trivial, so I'm just trying to show both abstract and resumo together on the description navtab and the resumo on the sort description (right below the title on the recordpage). Which files should I change and how (If i may ask) to have this behaviour? Also, I don't believe the way Dspace is exporting the abstract is correct, If i'm not wrong the pt-br abstract should be inside a field like dc.description xml:lang="pt" instead of creating a new tag. But I still have to check this and see if VuFind responds to this "correct" way. ---I also would like to aks another thing non related Is there some type of [secondary] "todo" list of VuFind, like with things for those interested and help and don't know where? I'm asking this because I know 3 features that would be appreciated, altough not very important, in VuFind so far: * Comments section integrated with social networks (I saw that VuFind had these but it got dropped some time ago). * Customize date range in the facets (I said I was gonna take care of that, but right now I have to finish the abnt citation and don't have a lot of free time) * Shows the dc fields corresponding with locale selected (as said in the last paragraph of the other subject) Samuel Henrique O. P. [samueloph] Técnico em Informática - UTFPR [2012]. Estudante de Engenharia de Computação - UTFPR. |