EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #02767
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Summary page - available metadata
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: Summary page - available metadata
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Date: Fri, 14 Mar 2014 10:50:17 +0000
Okay, that’s working great - extrapolating out from this, how would I then tap into other data? For example, we’d like to output a list of editors onto the abstract page if the EPrint is a book. I know how to do the conditional check for the type, I can see how to iterate through a number of objects, but I’m not sure how to retrieve those objects. Once we have them, I then presume that the theory is the same of using a citation template with relative fields to extract data from the database. On 14/03/2014 10:01, "John Salter" <J.Salter@leeds.ac.uk> wrote: >If you're getting an EPScript error, take a look in the Apache error log >- there may be something useful in there. >This is the relevant wiki page: http://wiki.eprints.org/w/EPScript (maybe >the 'Language Synopsis' section is the key to what you're doing wrong?) > >I'd recommend going down the route (as Tommy hinted at) of making a >citation for the document (in >..../cfg/citations/document/myLovelyCitation.xml) and using that e.g. ><epc:print expr="$doc.citation('default')" /> or <epc:print >expr="$doc.citation(' myLovelyCitation')" /> > >If none of that helps, show us what you've got and we may be able to help >more! > >Cheers, >John > > >-----Original Message----- >From: eprints-tech-bounces@ecs.soton.ac.uk >[mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andrew Beeken >Sent: 14 March 2014 09:19 >To: eprints-tech@ecs.soton.ac.uk >Subject: [EP-tech] Re: Summary page - available metadata > >Thanks Tommy, > >In principle I see how this should work, however all I¹m getting when I >try to do anything here is an [error in script] output. > >For example, in <archive>/cfg/citations/eprint/summary_page.xml, the >documents appear to be iterated through in a set (line 31) with the >outputs handled as $doc.some_function(). This does not seem to correlate >with being able to simply use database names in the output and when I try >$doc.some_database_field() the error is generated. I¹ve also tried simply >using the field as is but to no avail. > > > >On 13/03/2014 18:47, "Tommy Ingulfsen" <tommy@library.caltech.edu> wrote: > >>I assume you're using the EPrints Control Format (summary.xml)? >> >>If so, look at perl_lib/EPrints/Script.pm to see the various functions >>you >>can call on your object. For the metadata available for a document (as >>opposed to an eprint) I would take a look at >>archives/<archivename>/cfg/citations/document/*.xml. That should show >>that >>you can just use the field names from the 'document' database table like >>so: >> >><epc:print expr="fieldname"/> >> >>Does that help at all? >> >>tommy >> >>On 3/12/14 5:37 AM, "Andrew Beeken" <anbeeken@lincoln.ac.uk> wrote: >> >>>Hello! >>> >>>Currently trying to make some alterations to our summary pages; is there >>>any kind of documentation available as to what metadata can be used >>>here, >>>specifically (in this instance) for documents. For example, I want to be >>>able to show the File Description and Title for a given document; I can >>>see WHERE to do this, but not the variables within the document object >>>to >>>use. >>> >>>Andrew >>> >>>The University of Lincoln, located in the heart of the city of Lincoln, >>>has established an international reputation based on high student >>>satisfaction, excellent graduate employment and world-class research. >>> >>>The information in this e-mail and any attachments may be confidential. >>>If you have received this email in error please notify the sender >>>immediately and remove it from your system. Do not disclose the contents >>>to another person or take copies. >>> >>>Email is not secure and may contain viruses. The University of Lincoln >>>makes every effort to ensure email is sent without viruses, but cannot >>>guarantee this and recommends recipients take appropriate precautions. >>> >>>The University may monitor email traffic data and content in accordance >>>with its policies and English law. Further information can be found at: >>>http://www.lincoln.ac.uk/legal. >>> >>>*** Options: >>>http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >>>*** Archive: http://www.eprints.org/tech.php/ >>>*** EPrints community wiki: http://wiki.eprints.org/ >>>*** EPrints developers Forum: http://forum.eprints.org/ >> >> >>*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >>*** Archive: http://www.eprints.org/tech.php/ >>*** EPrints community wiki: http://wiki.eprints.org/ >>*** EPrints developers Forum: http://forum.eprints.org/ > > >*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >*** Archive: http://www.eprints.org/tech.php/ >*** EPrints community wiki: http://wiki.eprints.org/ >*** EPrints developers Forum: http://forum.eprints.org/ > >*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >*** Archive: http://www.eprints.org/tech.php/ >*** EPrints community wiki: http://wiki.eprints.org/ >*** EPrints developers Forum: http://forum.eprints.org/
- References:
- [EP-tech] Re: Summary page - available metadata
- From: Tommy Ingulfsen <tommy@library.caltech.edu>
- [EP-tech] Re: Summary page - available metadata
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- [EP-tech] Re: Summary page - available metadata
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] Re: Summary page - available metadata
- Prev by Date: [EP-tech] Re: Summary page - available metadata
- Next by Date: [EP-tech] EPrints Japanese 日本の
- Previous by thread: [EP-tech] Re: Summary page - available metadata
- Next by thread: [EP-tech] Re: Summary page - available metadata
- Index(es):