Advanced Customisation: Scripting EPrints

More documents

Recommendations

Info

Connecting to the Repository � Command line scripts (and CGI scripts) must explicitly connect to the repository by creating a new Session object � new(mode, repositoryid) �set mode to 1 for command line scripts �set mode to 0 for CGI scripts � And disconnect from the repository when complete � terminate() �performs necessary cleanup
Using Render Functions � XHTML is good for building Web pages � but not so good for command line output! �often no string equivalent � use tree_to_utf8() � extracts a string from the result of any rendering method � tree_to_utf8( eprint->render_citation)
Page 1 and 2: Advanced Customisation: Scripting E
Page 3 and 4: Roadmap � Core API � manipulati
Page 5 and 6: Putting it all together � Two ess
Page 7 and 8: Can manipulate tree to add extra te
Page 9 and 10: Render Methods: Session (2) � ren
Page 11 and 12: Render Methods: Session (4) � Man
Page 13 and 14: Rendering Methods: MetaFields � r
Page 15 and 16: Getting User Input (CGI parameters)
Page 17 and 18: Plugin Framework � EPrints provid
Page 19 and 20: Plugin Framework (3) � EPrints is
Page 21 and 22: Export Plugin: Registration � Reg
Page 23 and 24: Registration Example: FOAF $self->{
Page 25 and 26: Export Plugin: Conversion � For a
Page 27 and 28: Export Plugin: Template �� Regi
Page 29 and 30: Scripting Techniques: Writing Scree
Page 31 and 32: Screen Plugin: Registration � Reg
Page 33 and 34: Registration Example: EPrint Detail
Page 35 and 36: Screen Plugin: Define Functionality
Page 37 and 38: Screen Plugin Template: Render Only
Page 39 and 40: Screen Plugin Template: Combined
Page 41: Command Line Scripts � Usually st
Page 45 and 46: Example: lift_embargos � Removes
Page 47 and 48: CGI Scripts � Usually stored in c
Page 49: Summary � Use the core API to man

Advanced Customisation: Scripting EPrints

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?