EPrints Technical Mailing List Archive
Message: #00072
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] multilang eprints.* fields show up as HASH(0xhexnumber) in html head
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] multilang eprints.* fields show up as HASH(0xhexnumber) in html head
- From: Dobrica Pavlinušić <dpavlin@gmail.com>
- Date: Fri, 2 Mar 2012 15:49:33 +0100
We are using eprints 3.3.8 from Debian package and decided to use multilang fields for title, keywords and abstracts to provide English translation along with our Croatian originals. However, when EPrints generates <meta> tags we get something like this: <meta name="eprints.title" content="HASH(0xfc3107a8)" /> <meta name="eprints.ispublished" content="submitted" /> <meta name="eprints.subjects" content="SOC" /> <meta name="eprints.full_text_status" content="public" /> <meta name="eprints.keywords" content="HASH(0xfc236248)" /> <meta name="eprints.keywords" content="HASH(0xfc301f40)" /> <meta name="eprints.abstract" content="HASH(0xfc315c48)" /> <meta name="eprints.abstract" content="HASH(0xfc330770)" /> This makes *some* sense, because we have one title, and multilang keywords and abstract for this entry, however I would love to have text inside content. This is especially bad for Google Scholar and other crawlers (including Zoterro) which seem to prefer eprints.* meta fields as opposed to DC.title and/or DC.subject. I should also stress out that DC.* meta fileds are correctly generated (once, using default language to select one of available values). I did try to find my way through source code using grep, but I'm stuck where to look. Any help is greatly appreciated. -- ...2share!2flame... http://blog.rot13.org
- Prev by Date: [EP-tech] Re: FW: Directories on izual
- Next by Date: [EP-tech] Re: EPrints behind a reverse proxy
- Previous by thread: [EP-tech] Re: FW: Directories on izual
- Next by thread: [EP-tech] Re: multilang eprints.* fields show up as HASH(0xhexnumber) in html head
- Index(es):