https://wiki.eprints.org/w/api.php?action=feedcontributions&user=Ckeene&feedformat=atomEPrints Documentation - User contributions [en-gb]2024-03-28T08:40:14ZUser contributionsMediaWiki 1.31.8https://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=6216User:Ckeene/ep3 upgrade2008-12-01T10:38:41Z<p>Ckeene: </p>
<hr />
<div>Note: <br />
For some reason: "sudo /etc/init.d/apache2 stop" and "sudo /etc/init.d/apache2 start" not working, use sudo /usr/sbin/apache2ctl start instead.<br />
<br />
== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks they are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.<br />
# generate_abstracts<br />
# move mouse over a pdf icon in the web interface, thumbnail appears! it now works.<br />
<br />
== upgrade to 3.1 ==<br />
* in June 2008 it was upgrade to 3.1rc1 then rc2. This was quick and straight forward.<br />
* changed port from 8082 to 8080...<br />
** sudo vi /etc/apache2/ports.conf <br />
** /opt/eprints3/bin/epadmin config_core ep3v (had to re-enter a load of stuff again)<br />
** /opt/eprints3/bin/generate_apacheconf<br />
** edited firewall to allow 8080 (I hate linux firewalls!)<br />
<br />
== ldap ==<br />
Things to do<br />
* Existing users; will be imported via the import script from ep2<br />
* set up ldap authentication<br />
* use script i created for ep2 for new users</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6163User:Ckeene/Ideas for future versions of eprints2008-07-03T16:18:39Z<p>Ckeene: </p>
<hr />
<div>'''''Disclaimer: I know the eprints team is small, doing very cool stuff, have lots of ideas of their own and, of course, eprints is free! This is all just 'what I would like to see', while appreciating that these things may not be coming any time soon, or are not the direction the rest of the eprints community want to go in.'''''<br />
<br />
== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
* ''All of these are examples of creating documents and revising documents and sharing documents. This isn't too far from what a repository is. We have thought about helping integrate with the desktop by supporting WebDAV.'' [LES CARR]<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
* ''I think this is already what we do with eprints.ecs, as al authentication is handled by a single login page. I will check with Chris'' [LES CARR]<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!).<br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
* ''But you can already do all these things. That's why we have ids attached to authors, not just their names. You can View by Author IDs, and produce complete lists of an individual's research. As you point out there are USER objects which you could provide a bigger role for, beyond identifying the depositor as they do now.'' [LES CARR]<br />
<br />
== Enhance the eprint abstract page (a la flickr) ==<br />
the Eprints team briefly demonstrated this at OR08. It looked great.<br />
<br />
* ''Here's a mockup [http://users.ecs.soton.ac.uk/jtp/projects/ePrints/index4.html Abstract page]'' [LES CARR]<br />
<br />
Basically two things:<br />
* At the moment many people come in via google, land on a page and that is it. If the Abstract page had 'see similar items' 'people who looked at this also looked at', plus tags etc for enhanced navigation. As well as these autogenerated facilities, perhaps something where repository managers can say 'if a record belongs to chemistry then advertise item x, or display this promotional image/text).<br />
* Something I know has been discussed is the idea that it is the item that is import. for documents, a large preview, for images and movies, they should be shown on the page. Again, I know people often refer to flick as a way of showing the content, with the metadata still visible but not dominant, and I would add my vote in saying this sounds like the right direction.<br />
<br />
== One Repository, multiple views (long term?) ==<br />
At the moment eprints has the model: One repository database has one user interface. <br />
<br />
I think there is scope in changing this to one repository, many interfaces. I include deposit/user area, branding, and certain config in with 'interface'. <br />
<br />
* Some Universities have created separate etheses repositories, surely it would be better if everything was in one database, but they were able to create a separate interface. So that theses would see a user area just for them, with unique branding, etc. Postgrad Office may want a unique deposit/management process for theses and not just the generic deposit process.<br />
* Some Universities have semi-autonomous units who have their own branding and organisation. These units may toy with a respository, but want to do it there way, with their deposit process, branding, a search just for their items. etc (but may be happy with the idea that their research shows up in the main repository as well. this would allow them to create a second interface to do accommodate them, rather than them creating their own repository.<br />
* Repository Managers go to departments to try and encourage them to make use of the IR. A Department may be interested, but again, want specific browse views and searches that can appear on their departmental pages, (they may, for example hate the idea of unpublished items showing up with published ones, or only want their items to show). The ability to say 'sure we can set that up' is a huge plus.<br />
<br />
Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!<br />
<br />
* ''There is a general issue of making special collections a lot easier to manage, and that is something that we are working on. (That will support research groups and journals as well as scholarly collections.) However the issue of allowing groups to have their own listings on their own pages is often better supported by allowing them to import blank (unbranded) listings from the repository which are then branded by the local site using stylesheets. This puts control of the department/research group's pages into their hands, which makes them happy.'' [LES CARR]<br />
* CJK July 2008: looks like 3.1 will have the option of additional templates. http://wiki.eprints.org/w/New_Features_in_EPrints_3.1#Templates a good start (though still think there is more scope here and so leaving this on this list, for example the idea that someone could go to eprints.uni.edu/etheses/ and search/browse just theses in a completely different looking system and when they click on deposit see a different set of fields customised for thesis submission).<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
* ''We attempted this in an old JISC Project called "EPrints UK" using Dewey instead of LOC, but it relied on an experimental service from OCLC. If anyone could point us at such a service for LoC we would happily use it! '' [LES CARR]<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Youtube style embedded player for video/av items ==<br />
We want to encourage people to upload av and video research/teaching content. If they upload it to youtube (or the million other clone services) it looks cool. If they upload it to eprints, it looks like a file icon.<br />
<br />
Feature: a plugin to alter the abstract pages of multimedia content to have an embeded (flash) player similar to youtube.<br />
<br />
(July 2008)<br />
<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6162User:Ckeene/Ideas for future versions of eprints2008-07-03T16:10:46Z<p>Ckeene: /* One Repository, multiple views (long term?) */</p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
* ''All of these are examples of creating documents and revising documents and sharing documents. This isn't too far from what a repository is. We have thought about helping integrate with the desktop by supporting WebDAV.'' [LES CARR]<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
* ''I think this is already what we do with eprints.ecs, as al authentication is handled by a single login page. I will check with Chris'' [LES CARR]<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!).<br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
* ''But you can already do all these things. That's why we have ids attached to authors, not just their names. You can View by Author IDs, and produce complete lists of an individual's research. As you point out there are USER objects which you could provide a bigger role for, beyond identifying the depositor as they do now.'' [LES CARR]<br />
<br />
== Enhance the eprint abstract page (a la flickr) ==<br />
the Eprints team briefly demonstrated this at OR08. It looked great.<br />
<br />
* ''Here's a mockup [http://users.ecs.soton.ac.uk/jtp/projects/ePrints/index4.html Abstract page]'' [LES CARR]<br />
<br />
Basically two things:<br />
* At the moment many people come in via google, land on a page and that is it. If the Abstract page had 'see similar items' 'people who looked at this also looked at', plus tags etc for enhanced navigation. As well as these autogenerated facilities, perhaps something where repository managers can say 'if a record belongs to chemistry then advertise item x, or display this promotional image/text).<br />
* Something I know has been discussed is the idea that it is the item that is import. for documents, a large preview, for images and movies, they should be shown on the page. Again, I know people often refer to flick as a way of showing the content, with the metadata still visible but not dominant, and I would add my vote in saying this sounds like the right direction.<br />
<br />
== One Repository, multiple views (long term?) ==<br />
At the moment eprints has the model: One repository database has one user interface. <br />
<br />
I think there is scope in changing this to one repository, many interfaces. I include deposit/user area, branding, and certain config in with 'interface'. <br />
<br />
* Some Universities have created separate etheses repositories, surely it would be better if everything was in one database, but they were able to create a separate interface. So that theses would see a user area just for them, with unique branding, etc. Postgrad Office may want a unique deposit/management process for theses and not just the generic deposit process.<br />
* Some Universities have semi-autonomous units who have their own branding and organisation. These units may toy with a respository, but want to do it there way, with their deposit process, branding, a search just for their items. etc (but may be happy with the idea that their research shows up in the main repository as well. this would allow them to create a second interface to do accommodate them, rather than them creating their own repository.<br />
* Repository Managers go to departments to try and encourage them to make use of the IR. A Department may be interested, but again, want specific browse views and searches that can appear on their departmental pages, (they may, for example hate the idea of unpublished items showing up with published ones, or only want their items to show). The ability to say 'sure we can set that up' is a huge plus.<br />
<br />
Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!<br />
<br />
* ''There is a general issue of making special collections a lot easier to manage, and that is something that we are working on. (That will support research groups and journals as well as scholarly collections.) However the issue of allowing groups to have their own listings on their own pages is often better supported by allowing them to import blank (unbranded) listings from the repository which are then branded by the local site using stylesheets. This puts control of the department/research group's pages into their hands, which makes them happy.'' [LES CARR]<br />
* CJK July 2008: looks like 3.1 will have the option of additional templates. http://wiki.eprints.org/w/New_Features_in_EPrints_3.1#Templates a good start (though still think there is more scope here and so leaving this on this list, for example the idea that someone could go to eprints.uni.edu/etheses/ and search/browse just theses in a completely different looking system and when they click on deposit see a different set of fields customised for thesis submission).<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
* ''We attempted this in an old JISC Project called "EPrints UK" using Dewey instead of LOC, but it relied on an experimental service from OCLC. If anyone could point us at such a service for LoC we would happily use it! '' [LES CARR]<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Youtube style embedded player for video/av items ==<br />
We want to encourage people to upload av and video research/teaching content. If they upload it to youtube (or the million other clone services) it looks cool. If they upload it to eprints, it looks like a file icon.<br />
<br />
Feature: a plugin to alter the abstract pages of multimedia content to have an embeded (flash) player similar to youtube.<br />
<br />
(July 2008)<br />
<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6161User:Ckeene/Ideas for future versions of eprints2008-07-03T16:06:33Z<p>Ckeene: added youtube embedded player idea</p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
* ''All of these are examples of creating documents and revising documents and sharing documents. This isn't too far from what a repository is. We have thought about helping integrate with the desktop by supporting WebDAV.'' [LES CARR]<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
* ''I think this is already what we do with eprints.ecs, as al authentication is handled by a single login page. I will check with Chris'' [LES CARR]<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!).<br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
* ''But you can already do all these things. That's why we have ids attached to authors, not just their names. You can View by Author IDs, and produce complete lists of an individual's research. As you point out there are USER objects which you could provide a bigger role for, beyond identifying the depositor as they do now.'' [LES CARR]<br />
<br />
== Enhance the eprint abstract page (a la flickr) ==<br />
the Eprints team briefly demonstrated this at OR08. It looked great.<br />
<br />
* ''Here's a mockup [http://users.ecs.soton.ac.uk/jtp/projects/ePrints/index4.html Abstract page]'' [LES CARR]<br />
<br />
Basically two things:<br />
* At the moment many people come in via google, land on a page and that is it. If the Abstract page had 'see similar items' 'people who looked at this also looked at', plus tags etc for enhanced navigation. As well as these autogenerated facilities, perhaps something where repository managers can say 'if a record belongs to chemistry then advertise item x, or display this promotional image/text).<br />
* Something I know has been discussed is the idea that it is the item that is import. for documents, a large preview, for images and movies, they should be shown on the page. Again, I know people often refer to flick as a way of showing the content, with the metadata still visible but not dominant, and I would add my vote in saying this sounds like the right direction.<br />
<br />
== One Repository, multiple views (long term?) ==<br />
At the moment eprints has the model: One repository database has one user interface. <br />
<br />
I think there is scope in changing this to one repository, many interfaces. I include deposit/user area, branding, and certain config in with 'interface'. <br />
<br />
* Some Universities have created separate etheses repositories, surely it would be better if everything was in one database, but they were able to create a separate interface. So that theses would see a user area just for them, with unique branding, etc. Postgrad Office may want a unique deposit/management process for theses and not just the generic deposit process.<br />
* Some Universities have semi-autonomous units who have their own branding and organisation. These units may toy with a respository, but want to do it there way, with their deposit process, branding, a search just for their items. etc (but may be happy with the idea that their research shows up in the main repository as well. this would allow them to create a second interface to do accommodate them, rather than them creating their own repository.<br />
* Repository Managers go to departments to try and encourage them to make use of the IR. A Department may be interested, but again, want specific browse views and searches that can appear on their departmental pages, (they may, for example hate the idea of unpublished items showing up with published ones, or only want their items to show). The ability to say 'sure we can set that up' is a huge plus.<br />
<br />
Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!<br />
<br />
* ''There is a general issue of making special collections a lot easier to manage, and that is something that we are working on. (That will support research groups and journals as well as scholarly collections.) However the issue of allowing groups to have their own listings on their own pages is often better supported by allowing them to import blank (unbranded) listings from the repository which are then branded by the local site using stylesheets. This puts control of the department/research group's pages into their hands, which makes them happy.'' [LES CARR]<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
* ''We attempted this in an old JISC Project called "EPrints UK" using Dewey instead of LOC, but it relied on an experimental service from OCLC. If anyone could point us at such a service for LoC we would happily use it! '' [LES CARR]<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Youtube style embedded player for video/av items ==<br />
We want to encourage people to upload av and video research/teaching content. If they upload it to youtube (or the million other clone services) it looks cool. If they upload it to eprints, it looks like a file icon.<br />
<br />
Feature: a plugin to alter the abstract pages of multimedia content to have an embeded (flash) player similar to youtube.<br />
<br />
(July 2008)<br />
<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene&diff=6160User:Ckeene2008-07-03T15:57:39Z<p>Ckeene: </p>
<hr />
<div>[[Ideas for future versions of eprints]]<br />
== Chris Keene ==<br />
Chris Keene. <br />
Technical Development Manager, <br />
University of Sussex Library, <br />
UK.<br />
http://www.sussex.ac.uk/library/<br />
<br />
== Eprints 3 upgrade ==<br />
I'm keeping a journal of our upgrade/migration from eprints2 to '''eprints3''': [[User:Ckeene/ep3_upgrade]]<br />
<br />
== Ideas for future features in eprints ==<br />
I'm keeping a list of features (and infrastructure changes) I would like to see in eprints.<br />
[[User:Ckeene/Ideas for future versions of eprints]]<br />
<br />
== Stuff I've done related to eprints ==<br />
# I manage http://eprints.sussex.ac.uk for the University of Sussex <br />
# We have some background information http://www.sussex.ac.uk/library/ir/<br />
# and a not very much updated news/blog http://researchonline.lib.sussex.ac.uk/<br />
# I have made available some very simple analog config files and perl scripts for producing web usage statistics: [[Files/Simple_usage_statistics_(using_analog)]]<br />
# I made a tiny change to [[Files/Import_BibTeX_via_CGI]] to fix a bug<br />
# When working on something which is new to me related to eprints, I try to update the wiki to expand on anything unclear or missing. [[Special:Contributions/Ckeene]]<br />
<br />
== misc ==<br />
A Test:<br />
[[User:Ckeene/page2]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Https3&diff=6139Https32008-06-23T14:20:19Z<p>Ckeene: /* Introduction */ made 3.0.5 3.1 line bold</p>
<hr />
<div>== Introduction ==<br />
<br />
'''EPrints 3.0.5/3.1 introduces a new mechanism to set up HTTPS that greatly simplifies the process, see [[HTTPS]].'''<br />
<br />
<br />
Setting up EPrints3 to work with https is a little tricky. There seems to be a few bugs to be worked round. This How To considers the following scenario:<br />
<br />
* Two repositories, repos1 and repos2, being served by virtual hosts repos1.FQDN:80 and repos2.FQDN:80<br />
<br />
* A single https domain, at eprints.FQDN:443 (so that only one certificate is needed). Secure pages for repos1 and repos2 will be accessed at eprints.FQDN:443/repos1 and eprints.FQDN:443/repos2 respectively.<br />
<br />
This How To should work with EPrints 3.0 or 3.0.1. It was developed on Ubuntu Server 6.06, but should work on other systems without significant changes. The instructions can be adapted for an arbitrary number of repositories.<br />
<br />
It is assumed that EPrints is installed in /opt/eprints3/.<br />
<br />
== Getting started ==<br />
<br />
Install EPrints 3.x following the appropriate instructions.<br />
<br />
Run bin/epadmin create twice to create repos1 and repos2.<br />
<br />
Edit /opt/eprints3/archives/repos1/cfg/cfg.d/10_core.pl to read:<br />
<br />
$c->{host} = 'repos1.FQDN';<br />
$c->{port} = 80;<br />
$c->{aliases} = [];<br />
$c->{securehost} = 'eprints.FQDN';<br />
$c->{securepath} = '/repos1';<br />
$c->{secureport} = 443;<br />
<br />
<br />
Make secure versions of the templates:<br />
<br />
cp /opt/eprints3/archives/repos1/cfg/lang/en/templates/default.xml /opt/eprints3/archives/repos1/cfg/lang/en/templates/secure.xml<br />
<br />
Repeat these steps for repos2.<br />
<br />
Generate the Apache configuration:<br />
<br />
/opt/eprints3/bin/generate_apacheconf<br />
<br />
Add 'Include /opt/eprints3/cfg/apache.conf' to the Apache configuration (for Ubuntu / Debian, can replace everything in /etc/apache/sites-avaliable/default with 'Include /opt/eprints3/cfg/apache.conf'). Apache should now be correctly configured to serve the non-secure pages.<br />
<br />
== Secure Apache Configuration ==<br />
<br />
Next, we want to configure Apache to serve the secure pages. However, generate_apacheconf hasn't created a secure.conf file in /opt/eprints3/cfg/ so this needs to be done manually. Some configuration has been generated for us in /opt/eprints3/archives/repos1/var/auto-secure.conf and /opt/eprints3/archives/repos2/var/auto-secure.conf, but there are some problems with this:<br />
<br />
* Some sections of the configuration overlap;<br />
* The EPrints_ArchiveID and PerlSetVar EPrints_Secure variables have not been set.<br />
<br />
We'll therefore create our own configuration. Create a new file called cfg/secure.conf:<br />
<br />
#cfg/secure.conf:<br />
NameVirtualHost *:443<br />
<VirtualHost *:443><br />
ServerAdmin itsupport@FQDN<br />
ServerName eprints.FQDN<br />
<br />
SSLEngine On<br />
SSLCertificateFile /etc/apache2/ssl/apache.pem<br />
<br />
ErrorLog /var/log/apache2/error.log<br />
<br />
# Possible values include: debug, info, notice, warn, error, crit,<br />
# alert, emerg.<br />
LogLevel warn<br />
<br />
CustomLog /var/log/apache2/access.log combined<br />
ServerSignature On<br />
<br />
DocumentRoot "/var/www/eprints"<br />
<br />
<Directory "/opt/eprints3/cgi/users"><br />
AuthName "User Area"<br />
AuthType "Basic"<br />
PerlAuthenHandler EPrints::Apache::Auth::authen<br />
PerlAuthzHandler EPrints::Apache::Auth::authz<br />
require valid-user<br />
<br />
SetHandler perl-script<br />
PerlHandler ModPerl::Registry<br />
PerlSendHeader Off<br />
Options ExecCGI FollowSymLinks<br />
</Directory><br />
<Directory "/opt/eprints3/cgi/users/awstats"><br />
PerlSendHeader On<br />
</Directory><br />
<br />
<Directory "/opt/eprints3/cgi"><br />
SetHandler perl-script<br />
PerlHandler ModPerl::Registry<br />
PerlSendHeader Off<br />
Options ExecCGI FollowSymLinks<br />
</Directory><br />
<br />
PerlTransHandler EPrints::Apache::Rewrite<br />
<br />
Include /opt/eprints3/archives/repos1/var/manual-secure.conf <br />
Include /opt/eprints3/archives/repos2/var/manual-secure.conf<br />
</VirtualHost><br />
<br />
Not the line 'DocumentRoot "/var/www/eprints"'. Create an index.html file in /var/www/eprints/ with a welcome message and links to the home pages of the repositories. Also note that we need to create a manual-secure.conf file for each repository. The contents of this file are as follows:<br />
<br />
#/opt/eprints3/archives/repos1s/var/manual-secure.conf<br />
<br />
<Location "/repos1"><br />
PerlSetVar EPrints_ArchiveID repos1<br />
PerlSetVar EPrints_Secure yes<br />
PerlSetVar EPrints_Dir_SecuredCGI /opt/eprints3/cgi/users<br />
PerlSetVar EPrints_Dir_Documents /opt/eprints3/archives/repos1/documents<br />
PerlLogHandler EPrints::Apache::LogHandler<br />
</Location><br />
<br />
Alias /repos1/cgi/accounts/confirm /opt/eprints3/cgi/confirm<br />
Alias /repos1/cgi/accounts/register /opt/eprints3/cgi/register<br />
Alias /repos1/cgi/accounts/reset_password /opt/eprints3/cgi/reset_password<br />
Alias /repos1/cgi/accounts/set_password /opt/eprints3/cgi/set_password<br />
Alias /repos1/cgi/users/ /opt/eprints3/cgi/users/<br />
Alias /repos1/ /opt/eprints3/archives/publications/html/<br />
<br />
For completeness, we'll also want to add the welcome page to http: Add the following lines to /opt/eprints3/cfg/apache.conf<br />
<br />
<VirtualHost *:80><br />
ServerName eprints.FQDN<br />
ServerAdmin itsupport@FQDN<br />
DocumentRoot "/var/www/eprints"<br />
</VirtualHost><br />
<br />
Add 'Include /opt/eprints3/cfg/secure.conf' to the Apache configuration.<br />
<br />
One thing remains. In /opt/eprints3/archives/repos1/cfg/cfg.d/misc.pl and /opt/eprints3/archives/repos2/cfg/cfg.d/misc.pl change the line<br />
<br />
$c->{cookie_domain} = $c->{host}; <br />
<br />
to read<br />
<br />
$c->{cookie_domain} = $c->{securehost}; <br />
<br />
Restart Apache. At this point it should be possible to access the repositories at http://publications.modhist.ox.ac.uk and http://oxhistonline.modhist.ox.ac.uk and log in to the secure area. <br />
<br />
=== Debian / Ubuntu specific SSL instructions ===<br />
<br />
Create a file called ssl in /etc/apache2/sites-available/ssl and add the line 'Include /opt/eprints3/cfg/secure.conf'. Run the commands:<br />
<br />
a2ensite ssl<br />
a2enmod ssl<br />
apache2-ssl-certificate<br />
echo "Listen 443" >> /etc/apache2/ports.conf<br />
<br />
<br />
== Bugs ==<br />
<br />
=== Broken Actions ===<br />
<br />
Links which call Perl cgi scripts are broken – e.g. Under Manage Deposits, click New Item. Select an Item Type and then click Next. You will be returned to the Manage Deposits page, rather than to the next step in the workflow. This appears to be because the form action is pointing to http://publications.modhist.ox.ac.uk/cgi/users/home#t rather than /publications/cgi/users/home. As far as I can see, this is a bug, rather than a configuration mistake, though I'm happy to be advised otherwise.<br />
<br />
The workaround I have for this bug is to install patch 252, which can be downloaded from http://files.eprints.org/252/<br />
<br />
The patch seeks to resolve the problem by introducing a configuration variable users_url in 20_baseurls.pl. The use of perl_url has been replaced with users_url for all links to scripts in cgi/users. For insecure use, users_url can be set to perl_url. When https is requires, it can be adjusted appropriately.<br />
<br />
Apply the patch to the EPrints 3.x source (patch -d eprints-3.0/ -p0 < users-url.patch) and re-run configure and install.pl. Add the following lines to /opt/eprints3/archives/repos1/cfg/cfg.d/20_baseurls.pl :<br />
<br />
$c->{secure_urlpath} = $c->{securepath};<br />
$c->{secure_url} = "https://".$c->{securehost}.($c->{secureport}!=443?":".$c->{secureport}:"").$c->{secure_urlpath};<br />
<br />
# Mod_perl scripts for users scripts<br />
# If not using https, make this the same as perl_url<br />
# Otherwise make it $c->{secure_url}."/cgi"<br />
#$c->{users_url} = $c->{perl_url};<br />
$c->{users_url} = $c->{secure_url}."/cgi";<br />
<br />
Similarly for /opt/eprints3/archives/repos2/cfg/cfg.d/20_baseurls.pl. Restart Apache. It should now be possible to upload documents, step through workflows etc.<br />
<br />
However, some bugs with image urls remain.<br />
<br />
=== Internet Explorer 'Secure and non Secure items' ===<br />
<br />
We're not done yet! Internet Explorer complains if non-secure (http) and secure (https) items are displayed on the same page. This happens when a full url, beginning http:// is embedded in a page that is https. If the securepath and url_path variables were the same, e.g. we were using http://repos1.FQDN/repos1 and https://eprints.FQDN/repos1 then we could simply make all urls relative, but because they are different, e.g http://repos1.FQDN/ and https://eprints.FQDN/repos1 we must handle the secure and non-secure cases separately.<br />
<br />
Edit /opt/eprints3/archives/repos1/cfg/lang/en/templates/secure.xml to use full https:// urls for included javascript and css and for the logo and .ico files. The head section should look something like this:<br />
<br />
<head><br />
<title><epc:pin ref="title" textonly="yes"/> - <epc:phrase ref="archive_name"/></title><br />
<script src="{$config{secure_url}}/javascript/auto.js" type="text/javascript"><!-- nope --></script><br />
<style type="text/css" media="screen">@import url(<epc:print expr="$config{secure_url}"/>/style/secure_auto.css);</style><br />
<style type="text/css" media="print">@import url(<epc:print expr="$config{secure_url}"/>/style/print.css);</style><br />
<link rel="icon" href="{$config{secure_url}}/favicon.ico" type="image/x-icon"/><br />
<link rel="shortcut icon" href="{$config{secure_url}}/favicon.ico" type="image/x-icon"/><br />
<link rel="Top" href="{$config{frontpage}}"/><br />
<link rel="Search" href="{$config{perl_url}}/search"/><br />
<epc:pin ref="head"/><br />
</head><br />
<body bgcolor="#ffffff" text="#000000"><br />
div class="ep_noprint"><br />
<noscript><style type='text/css'>@import url(<epc:print expr="$config{secure_url}"/>/style/nojs.css);</style></noscript><br />
</div><br />
<epc:pin ref="pagetop"/><br />
div class="ep_tm_header ep_noprint"><br />
div class="ep_tm_logo"><a href="{$config{frontpage}}"><img alt="Logo" src="{$config{secure_url}}{$config{site_logo}}" /></a></div><br />
<br />
also change the link to the EPrints logo in the footer:<br />
<br />
<a href="http://eprints.org/software/"><img src="{$config{secure_url}}/images/eprintslogo.gif" border="0"/></a><br />
<br />
We now need to modify 'generate_static' to create the secure_auto.css file as well as auto.css. The relevant section should be modified like this:<br />
<br />
# do the magic auto.js and auto.css<br />
my $js = "";<br />
my $css = "";<br />
my $secure_css ="";<br />
my $fn;<br />
my $base_url = $session->get_repository->get_conf( "base_url" );<br />
my $secure_url = $session->get_repository->get_conf( "secure_url" );<br />
foreach my $target ( sort keys %{$map} )<br />
{<br />
if( $target =~ m/(\/style\/auto\/.*\.css$)/ )<br />
{<br />
$css .= "\@import url($base_url$1);\n";<br />
$secure_css .= "\@import url($secure_url$1);\n";<br />
} <br />
if( $target =~ m/(\/javascript\/auto\/.*\.js$)/ )<br />
{<br />
$fn = $map->{$target};<br />
open( JS, $fn ) || EPrints::abort( "Can't read $fn: $!" );<br />
$js .= "\n\n\n/* From: $fn */\n\n";<br />
$js .= join( "", <JS> );<br />
close JS; } <br />
}<br />
<br />
$fn = "$base_target_dir/style/auto.css";<br />
open( CSS, ">$fn" ) || EPrints::abort( "Can't write $fn: $!" );<br />
$wrote_files->{$fn} = 1;<br />
print CSS $css;<br />
close CSS;<br />
<br />
$fn = "$base_target_dir/style/secure_auto.css";<br />
open( CSS, ">$fn" ) || EPrints::abort( "Can't write $fn: $!" );<br />
$wrote_files->{$fn} = 1;<br />
print CSS $secure_css;<br />
close CSS;<br />
<br />
Re-run generate_static repos1.<br />
<br />
=== Missing Images ===<br />
<br />
A number of image links will be broken because eprints is looking for them on urlpath rather than on secureurl. In some cases this can be fixed by replacing urlpath with secureurl in the code, but some phrases may appear on both secure and insecure pages. Therefore we also need a solution which can be evaluated by a epin in a template. The cleanest way I could find of doing this is as follows:<br />
<br />
Add two methods to EPrints::Session<br />
<br />
<br />
######################################################################<br />
=pod<br />
<br />
=item $foo = $session->get_baseurl()<br />
<br />
Gets the base url for images, depending on whether the session is secure<br />
or not (N.B. by secure we mean EPrints_secure is yes)<br />
Added by CSH 26 June 2007<br />
<br />
=cut<br />
######################################################################<br />
sub get_baseurl<br />
{<br />
my( $self ) = @_;<br />
<br />
my $esec = $self->get_request->dir_config( "EPrints_Secure" );<br />
if( defined $esec && $esec eq "yes" )<br />
{<br />
return $self->get_repository->get_conf( "securepath" );<br />
}<br />
else<br />
{<br />
return $self->get_repository->get_conf( "base_url" );<br />
} <br />
}<br />
<br />
######################################################################<br />
=pod<br />
<br />
=item $foo = $session->get_imageurl()<br />
<br />
Gets the base url for images, depending on whether the session is secure<br />
or not (N.B. by secure we mean EPrints_secure is yes)<br />
Added by CSH 26 June 2007<br />
<br />
=cut<br />
######################################################################<br />
sub get_imageurl<br />
{<br />
my( $self ) = @_;<br />
<br />
return $self->get_baseurl."/style/images/";<br />
} <br />
<br />
Search through the eprints code for every occurrence of the string /style/images/ and replace with a call to get_imageurl<br />
<br />
e.g. In /opt/eprints/perl_lib/EPrints/Plugin/Screen/Items.pm, change the line<br />
<br />
my $imagesurl = $self->{session}->get_repository->get_conf( "urlpath" )."/style/images";<br />
<br />
to<br />
<br />
my $imagesurl = $self->{session}->get_imageurl;<br />
<br />
<br />
We will add a variable called baseurl to the variables available in a script:<br />
<br />
In the execute method of EPrints::Script, add:<br />
<br />
$state->{baseurl} = [$state->{session}->get_baseurl, "STRING" ];<br />
<br />
before the run command is called on the compiler. It will now be possible to get the url for images in a phrase through {$baseurl}<br />
<br />
In /opt/eprints3/lib/lang/en/phrases/system.xml, change the links to images in the following phrases to use $baseurl<br />
<br />
sys:ep_form_required<br />
Plugin/InputForm/Surround/Default:show_help<br />
Plugin/InputForm/Surround/Default:hide_help<br />
lib/session:show_help<br />
lib/session:hide_help<br />
<br />
<br />
e.g. the ep_form_required phrase becomes:<br />
<br />
<epp:phrase id="sys:ep_form_required"><img src="{$baseurl}/style/images/required.png" border="0" class="ep_required" alt="Required"/>&nbsp;<epc:pin name="label"/></epp:phrase><br />
<br />
If some repositories aren't using https, you may prefer to override these phrases on a per repository basis.<br />
<br />
== Troubleshooting ==<br />
<br />
Some common problems and solutions:<br />
<br />
=== File does not exist: /htdocs ===<br />
<br />
In the log file you may see messages like:<br />
<br />
File does not exist: /htdocs<br />
<br />
This may be generated by https pages with invalid links to images (e.g. /images instead of /repos1/images) if no DocumentRoot is set for the https virtual host. Note that if we had only one repository per https address we could use DocumentRoot to point to DocumentRoot /opt/eprints3/archives/ARCHIVEID/html/en/ (as suggested by Peter Schober) but this wont work on a per repository base as you can’t put DocumentRoot in a Location block.<br />
<br />
=== EPrint 1 has no directory set ===<br />
<br />
If you get the message “EPrint 1 has no directory set. This is very dangerous as EPrints has no idea where to write files for this eprint. This may imply a buggy import tool or some other cause of corrupt data.” it probably means that you forgot to set Apache to run as eprints:eprints (or alternatively, add the Apache user to the eprints group).<br />
<br />
=== Other ===<br />
<br />
Remember to check that the EPrints_Dir_SecuredCGI and EPrints_Dir_Documents variables are set and cookie_domain is securehost not host.<br />
<br />
== Useful info ==<br />
<br />
You can set $imagesurl to be secure or insecure at runtime with some code like this (taken from MetaField.pm) <br />
<br />
my $esec = $session->get_request->dir_config( "EPrints_Secure" );<br />
if( defined $esec && $esec eq "yes" )<br />
{<br />
$imagesurl = $session->get_repository->get_conf( "securepath" )."/style/images";<br />
}</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=6138User:Ckeene/ep3 upgrade2008-06-23T14:06:05Z<p>Ckeene: ldap</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks they are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.<br />
# generate_abstracts<br />
# move mouse over a pdf icon in the web interface, thumbnail appears! it now works.<br />
<br />
== upgrade to 3.1 ==<br />
* in June 2008 it was upgrade to 3.1rc1 then rc2. This was quick and straight forward.<br />
* changed port from 8082 to 8080...<br />
** sudo vi /etc/apache2/ports.conf <br />
** /opt/eprints3/bin/epadmin config_core ep3v (had to re-enter a load of stuff again)<br />
** /opt/eprints3/bin/generate_apacheconf<br />
** edited firewall to allow 8080 (I hate linux firewalls!)<br />
<br />
== ldap ==<br />
Things to do<br />
* Existing users; will be imported via the import script from ep2<br />
* set up ldap authentication<br />
* use script i created for ep2 for new users</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=6137User:Ckeene/ep3 upgrade2008-06-23T13:08:17Z<p>Ckeene: /* upgrade to 3.1 */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks they are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.<br />
# generate_abstracts<br />
# move mouse over a pdf icon in the web interface, thumbnail appears! it now works.<br />
<br />
== upgrade to 3.1 ==<br />
* in June 2008 it was upgrade to 3.1rc1 then rc2. This was quick and straight forward.<br />
* changed port from 8082 to 8080...<br />
** sudo vi /etc/apache2/ports.conf <br />
** /opt/eprints3/bin/epadmin config_core ep3v (had to re-enter a load of stuff again)<br />
** /opt/eprints3/bin/generate_apacheconf<br />
** edited firewall to allow 8080 (I hate linux firewalls!)</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=6136User:Ckeene/ep3 upgrade2008-06-23T12:46:01Z<p>Ckeene: 3.1</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks they are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.<br />
# generate_abstracts<br />
# move mouse over a pdf icon in the web interface, thumbnail appears! it now works.<br />
<br />
== upgrade to 3.1 ==<br />
* in June 2008 it was upgrade to 3.1rc1 then rc2. This was quick and straight forward.<br />
* changed port from 8082 to 8080<br />
* sudo vi /etc/apache2/ports.conf <br />
* /opt/eprints3/bin/epadmin config_core ep3v (had to re-enter a load of stuff again)<br />
* /opt/eprints3/bin/generate_apacheconf</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Installing_in_a_chroot_Debian/Ubuntu&diff=6114Installing in a chroot Debian/Ubuntu2008-06-03T14:06:22Z<p>Ckeene: </p>
<hr />
<div>[[Category:Debian and Ubuntu]]<br />
These instructions were submitted to ePrints via the EP-Tech mailing list. They are based upon a users experience of installing eprints under a chroot from a 32-bit box running Ubuntu 7.04 Server.<br />
<br />
Please email ep-tech with any comments / suggestions on this process as this was written by a user and has not been verified by the eprints team.<br />
<br />
<br />
=chroot=<br />
<br />
chroot allows you to create a "virtual machine" inside of an actual machine with its own libraries. <br />
Here you can run separate copies of apache and eprints.<br />
<br />
==Step 1 - Install chroot==<br />
<br />
All commands need to be executed as root unless otherwise specified. Ubuntu users should prefix all commands with sudo.<br />
<br />
#apt-get install dchroot debootstrap<br />
#mkdir /chroot/<br />
<br />
Add this line to /etc/dchroot.conf:<br />
feisty /chroot<br />
<br />
execute:<br />
<br />
#debootstrap --arch i386 feisty /chroot<br />
#cp /var/lib/locales/supported.d/local /chroot/var/lib/locales/supported.d<br />
#chroot /chroot<br />
#dpkg-reconfigure locales<br />
<br />
==Step 2 - Configuring chroot==<br />
<br />
Add the following lines to /chroot/etc/apt/sources.list:<br />
<br />
deb http://archive.ubuntu.com/ubuntu feisty main restricted universe multiverse<br />
deb http://security.ubuntu.com/ubuntu feisty-security main restricted<br />
universe multiverse<br />
<br />
You can also add ONE of the following for ePrints:<br />
deb http://deb.eprints.org/ stable/<br />
or<br />
deb http://deb.eprints.org/ unstable/<br />
<br />
<br />
==Step 3 - Installing in the chroot==<br />
Change to your chroot by executing:<br />
#chroot /chroot<br />
Install the chroot:<br />
#apt-get update<br />
#apt-get upgrade<br />
<br />
==Step 4 - User Details==<br />
In ANOTHER terminal (or exit chroot):<br />
#cp /etc/passwd /chroot/etc/<br />
#cp /etc/shadow /chroot/etc/<br />
#cp /etc/group /chroot/etc/<br />
#cp /etc/sudoers /chroot/etc/<br />
#cp /etc/hosts /chroot/etc/<br />
<br />
==Step 5 - Home Areas and other directories==<br />
<br />
Add the following lines to /etc/fstab:<br />
/home /chroot/home none bind 0 0<br />
/tmp /chroot/tmp none bind 0 0<br />
/dev /chroot/dev none bind 0 0<br />
/proc /chroot/proc proc defaults 0 0<br />
/media/cdrom0 /chroot/media/cdrom0 none bind 0 0<br />
/usr/share/fonts /chroot/usr/share/fonts none bind 0 0<br />
<br />
There may be more depending on the setup of your system and how it mounts devices.<br />
<br />
==Step 6 - Finalalising Install of chroot==<br />
#mkdir /chroot/media/cdrom0<br />
#mkdir /chroot/usr/share/fonts<br />
#mount -a<br />
<br />
Add the following to /usr/local/bin/do_dchroot (new file):<br />
#!/bin/sh<br />
exec /usr/bin/dchroot -d "`echo $0 | sed 's|^.*/||'` `for i in "$@";<br />
do echo -n '"'$i'" '; done`"<br />
<br />
Then execute:<br />
<br />
#sudo chmod 755 /usr/local/bin/do_dchroot<br />
<br />
Access your chroot now as yourself by executing (not as root):<br />
user@box# dchroot -d<br />
<br />
==chroot graphical interface - optional==<br />
From your chroot. As root execute:<br />
#apt-get install synaptic<br />
#ln -s /usr/sbin/synaptic /usr/sbin/synaptic32<br />
<br />
Exit from your chroot:<br />
#exit<br />
<br />
Then:<br />
#ln -s /usr/local/bin/do_dchroot /usr/local/bin/synaptic32<br />
#synaptic32<br />
<br />
=Installing Eprints in a chroot=<br />
<br />
You can now follow the normal instructions from the many guides provided in [[Documentation]].<br />
<br />
<br />
If you added deb.eprints.org to your apt/sources.list then the following can be executed (as root):<br />
#apt-get install eprints<br />
<br />
Follow the Instructions.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_3_on_Debian&diff=6113Installing EPrints 3 on Debian2008-06-03T14:05:58Z<p>Ckeene: </p>
<hr />
<div>{{Installation}}<br />
[[Category:Debian and Ubuntu]]<br />
See also: [[Installing EPrints 3 via apt (Debian/Ubuntu)]]<br />
<br />
== Setting up Debain ==<br />
<br />
This instructions assume a working Debian ("Edgy Eft") installation (or close approximation thereof).<br />
<br />
== Install EPrints Dependencies ==<br />
<br />
<br />
Install Apache and mod_perl:<br />
<br />
root@debian$ apt-get install apach2-mpm-prefork libapache2-mod-perl2<br />
<br />
Install MySQL:<br />
<br />
root@debian$ apt-get install install mysql-server<br />
<br />
Install perl dependencies:<br />
<br />
root@debian$ apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl libxml-parser-perl.<br />
<br />
== Auxiliary Packages ==<br />
<br />
You need further packages for the seamless work of Eprints; these might or might not be installed on the system:<br />
<br />
Packages for building eprints:<br />
<br />
root@debian$ apt-get install gzip tar unzip make lynx wget ncftp ftp<br />
<br />
Programs for extracting content:<br />
<br />
root@debian$ apt-get install gs xpdf xv antiword elinks<br />
<br />
Programs making pictures, formulas, etc.<br />
<br />
root@debian$ apt-get install pdftk tetex-bin psutils imagemagick<br />
<br />
== Configuring MySQL ==<br />
<br />
It is strongly recommended that you set a root password in mysql:<br />
<br />
$ mysqladmin -u root password <new password><br />
<br />
== Create an 'eprints' system user ==<br />
root@debain$ adduser --system --home /opt/eprints3 --group eprints <br />
<br />
Add the 'www-data' user to the 'eprints' group:<br />
<br />
root@debain$ adduser www-data eprints<br />
<br />
== Install EPrints ==<br />
<br />
Download EPrints 3. Unpack and install the tarball:<br />
<br />
$ tar xzvf eprints-3.x.y.tar.gz<br />
$ cd eprints-3.x.y<br />
$ ./configure --with-smtp-server=smtp.yourdomain<br />
$ sudo ./install.pl<br />
<br />
== Set up Apache2 ==<br />
<br />
Add this line to <tt>/etc/apache2/sites-available/eprints</tt><br />
Include /opt/eprints3/cfg/apache.conf<br />
and enable the site<br />
$ sudo a2ensite eprints<br />
(this leaves <tt>/etc/apache2/apache.conf</tt> untouched, making future Apache upgrades easier)<br />
<br />
== Set up the indexer as a service ==<br />
<br />
$ sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
<br />
Make the indexer start automatically when the machine is rebooted:<br />
<br />
$ sudo update-rc.d epindexer defaults 99 99<br />
<br />
== Configure an archive ==<br />
<br />
Follow the steps in the main EPrints documentation to configure an archive.<br />
* [[Getting Started with EPrints 3]]<br />
<br />
== Restarting Apache ==<br />
<br />
$ sudo /etc/init.d/apache2 force-reload</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Debian_from_source&diff=6112Debian from source2008-06-03T14:05:32Z<p>Ckeene: </p>
<hr />
<div>This technique of installing EPrints allows you build your own debian package for eprints from our source (of the binary).<br />
<br />
==Configuring APT==<br />
<br />
Using your favorite text editor edit "/etc/apt/sources.list" and add the lines:<br />
<br />
deb http://deb.eprints.org/ unstable/<br />
deb-src http://deb.eprints.org/ source/<br />
<br />
The update your apt<br />
<br />
root@host$ apt-get update<br />
<br />
==Install build dependancies==<br />
<br />
This can now be done with one command:<br />
<br />
root@host$ apt-get build-dep eprints<br />
<br />
==Get EPrints source==<br />
<br />
root@host$ apt-get source eprints<br />
<br />
This will provide you with a tar.gz which is extracted to the current directory.<br />
<br />
==Rebuilding==<br />
<br />
To change the way the eprints builds you can edit the debian/rules file (the only line you will want is the configure one). Once done you can then type dpkg-buildpackage -rfakeroot from the root dir of the extracted tar ball. <br />
<br />
This will build you a .deb in the directory above your current location, which can then be installed usinging dpkg:<br />
<br />
dpkg -i ../eprints-X.X.X_all.deb<br />
<br />
<br />
Alternativly you can configure and install it yourself (a non debian specific version) by configuring manually and then running install.pl:<br />
<br />
$ ./configure --with-smtp-server=smtp.yourdomain<br />
$ sudo ./install.pl<br />
<br />
Note: The Ubuntu 7.04 kernel does not support the syscalls Eprints uses for determining the free disk size. Thus you must disable df as well:<br />
<br />
U7.04$ ./configure --with-smtp-server=smtp.yourdomain --disable-diskfree<br />
<br />
[[Category:Debian and Ubuntu]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=EPrints_Live_CD_Help&diff=6111EPrints Live CD Help2008-06-03T14:05:11Z<p>Ckeene: </p>
<hr />
<div>= Introduction = <br />
<br />
The EPrints3 Live CD is designed to help you experience EPrints without the need for a machine to run it on. The CD comes complete with a fully installed EPrints3 distribution which also has our own training archive already set up. It also contains a recent version of out training documentation and exercises as well as example material.<br />
<br />
From the environment the CD provides you can harness the full power of EPrints3 to setup your own archives for testing and also have an easy way to test new EPrints functionality without putting your active archive at risk. <br />
<br />
For new repository maintainers the Live CD can also be one click installed permanently onto your hard drive. This will enable you to preserve changes to your archives between reboots (without needing to use a memory stick).<br />
<br />
The Live CD really does provide the all in one solution for experiencing EPrints repository management software. <br />
<br />
The CD is currently only available for the x86 (32-bit) platforms and is based upon the Ubuntu Linux distribution.<br />
<br />
= Development News = <br />
<br />
The live CD is based upon the [http://www.ubuntu.com Ubuntu Linux Live CD] with Open Office removed to make available the space to install EPrints + all its dependencies whilst still remaining small enough to fit on a single CD. <br />
<br />
= Using the LIVE CD (Start Here) =<br />
<br />
* Download the image ([[Documentation#Download]]) and burn it to a cd using your favorite cd writing application. (Make cup of tea)<br />
* Boot PC from the CD. (Drink cup of tea)<br />
* (Not required with Live CD v.1.1) To prepare EPrints to run from the Live CD open a terminal (available from Applications->Accessories) and type the following:<br />
sudo setup_eprints_live<br />
* Open Firefox or similar browser and navigate to http://training.eprints.org (which is linked to your local machine, no net connection required)<br />
<br />
= To Install From the Live CD = <br />
<br />
* From a clean boot into the Live CD click the install icon. (Go make fresh coffee from ungrounded coffee beans)<br />
* Once installed and running from your hard drive execute the following from within a terminal:<br />
sudo touch /etc/apache2/httpd.conf<br />
sudo apache2ctl stop<br />
sudo apache2crl start<br />
* To enable the training archive:<br />
sudo echo "127.0.0.1 training.eprints.org training" >> /etc/hosts.conf<br />
<br />
= Storing your Archive on a Memory Stick =<br />
<br />
By using the live cd, any changes made will be lost when the system is shut down to avoid this we have created some scripts which backup your archive onto a memory stick.<br />
<br />
These scripts should be stored somewhere on the memory stick and the files are stored in a folder called "live_cd" relative to the position to the scripts.<br />
<br />
Extract [http://www.eprints.org/files/eprints3/mem_key/mem_key.zip this file] onto your memory stick and execute as root:<br />
<br />
== Archive only Backup ==<br />
This will only backup your archive, it will not include any of the global plugins or settings which apply to all repositories.<br />
root@ubuntu$ bash archive_to_usb.sh archive_name<br />
<br />
== Complete EPrints Tree Backup ==<br />
This will backup everything in your eprints3 tree.<br />
root@ubuntu$ bash all_to_usb.sh archive_name<br />
<br />
Don't forget to safely unmount the memory stick, on the live cd close any windows which popped up when the memory stick was inserted and then as root:<br />
root@ubuntu$ cd /<br />
root@ubuntu$ umount /media/disk<br />
<br />
=== Script Details ===<br />
<br />
The script backs up both your archive and the related database by doing the following, it assumes you have not set a root password on the mysql database:<br />
<br />
archive_to_usb.sh:<br />
<br />
#!/bin/bash<br />
if [ "$1" = "" ]<br />
then<br />
echo "No Archive Specified"<br />
else<br />
FOO=`pwd`<br />
mkdir "$FOO/live_cd"<br />
rm -fR "$FOO/live_cd/$1"<br />
mkdir "$FOO/live_cd/$1"<br />
tar -cf "$FOO/live_cd/$1/$1.tar" /usr/share/eprints3/archives/$1<br />
mysqldump -u root $1 > $FOO/live_cd/$1/$1.sql<br />
echo "DONE"<br />
fi<br />
<br />
all_to_usb.sh:<br />
<br />
#!/bin/bash<br />
if [ "$1" = "" ]<br />
then<br />
echo "No Archive Specified"<br />
else<br />
FOO=`pwd`<br />
mkdir "$FOO/live_cd"<br />
rm -fR "$FOO/live_cd/eprints3"<br />
mkdir "$FOO/live_cd/eprints3"<br />
rm -fR "$FOO/live_cd/$1"<br />
mkdir "$FOO/live_cd/$1"<br />
tar -cf "$FOO/live_cd/eprints3/eprints3.tar" /usr/share/eprints3/*<br />
mysqldump -u root $1 > "$FOO/live_cd/$1/$1.sql"<br />
echo "DONE"<br />
fi <br />
<br />
== Restoring your archive from memory stick ==<br />
<br />
Don't forget to follow the step above to configure ePrints to run from the live cd first!<br />
<br />
Locate the place where you extracted the files to previously on your memory stick and as root:<br />
<br />
== Archive Only ==<br />
root@ubuntu$ bash usb_to_archive.sh archive_name<br />
<br />
== Complete EPrints Tree ==<br />
root@ubuntu$ bash usb_to_all.sh archive_name <br />
<br />
=== Script Details ===<br />
<br />
Pretty much the opposite of the other script:<br />
<br />
usb_to_archive.sh:<br />
<br />
#!/bin/bash<br />
if [ "$1" = "" ]<br />
then<br />
echo "No Archive Specified"<br />
else<br />
FOO=`pwd`<br />
rm -fR /usr/share/eprints3/archives/$1<br />
tar -xf live_cd/$1/$1.tar -C /<br />
echo "drop database $1" | mysql -u root<br />
echo "create database $1" | mysql -u root<br />
mysql -u root $1 < live_cd/$1/$1.sql<br />
echo "DONE"<br />
fi <br />
<br />
usb_to_all.sh:<br />
<br />
#!/bin/bash<br />
if [ "$1" = "" ]<br />
then<br />
echo "No Archive Specified"<br />
else<br />
FOO=`pwd`<br />
rm -fR /usr/share/eprints3/<br />
tar -xf live_cd/eprints3/eprints3.tar -C /<br />
echo "drop database $1" | mysql -u root<br />
echo "create database $1" | mysql -u root<br />
mysql -u root $1 < live_cd/$1/$1.sql<br />
echo "DONE"<br />
fi<br />
<br />
= Troubleshooting =<br />
<br />
If you find any problems with the CD please contact myself (David Tarrant) dct05r[at]ecs.soton.ac.uk.<br />
<br />
Any problems with the EPrints software should be referred to the EPrints development team.<br />
<br />
[[Category:Debian and Ubuntu]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_Debian/Ubuntu&diff=6110Installing EPrints on Debian/Ubuntu2008-06-03T14:04:43Z<p>Ckeene: </p>
<hr />
<div>{{Installation}}<br />
[[Category:Debian and Ubuntu]]<br />
<br />
David Tarrant has built a Debian/Ubuntu package for Eprints.<br />
<br />
===Stable Release===<br />
<br />
Add the following to /etc/apt/sources.list:<br />
<br />
deb http://deb.eprints.org/ stable/<br />
deb-src http://deb.eprints.org/ source/<br />
<br />
===Unstable Release===<br />
<br />
To install the latest '''unstable''' release add the following to /etc/apt/sources.list:<br />
<br />
deb http://deb.eprints.org/ unstable/<br />
deb-src http://deb.eprints.org/ source/<br />
<br />
===*NEW* 3.1 Beta===<br />
To install the latest 3.1 '''unstable''' release add the following to /etc/apt/sources.list:<br />
<br />
deb http://deb.eprints.org/3.1/ unstable/<br />
deb http://deb.eprints.org/3.1/ source/<br />
<br />
Do '''not''' add both the stable and unstable repositories.<br />
<br />
===Installing Eprints via apt-get===<br />
<br />
To install Eprints and all its dependencies execute the following:<br />
<br />
apt-get update<br />
apt-get install eprints<br />
<br />
You should now have a working installation of eprints in /usr/share/eprints3/. Please follow the on-screen instructions to set up an eprints repository. You probably want to start with (as root):<br />
<br />
su eprints<br />
cd<br />
./bin/epadmin create<br />
logout<br />
a2ensite eprints3<br />
apache2ctl reload<br />
<br />
Known issues with the Debian/Ubuntu package can be found at [[Debian Known Issues]].<br />
<br />
===Getting and Compiling from Source===<br />
<br />
To install dependencies and retrieve the Eprints source execute the following:<br />
<br />
apt-get update<br />
apt-get build-dep eprints<br />
apt-get source eprints<br />
<br />
The source will be saved to a tarball in the current directory.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Category:Debian_and_Ubuntu&diff=6109Category:Debian and Ubuntu2008-06-03T14:03:50Z<p>Ckeene: New page: Pages that contain information for Debian and Ubuntu users</p>
<hr />
<div>Pages that contain information for Debian and Ubuntu users</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Debian_Known_Issues&diff=6107Debian Known Issues2008-06-03T14:00:07Z<p>Ckeene: debian and ubuntu category</p>
<hr />
<div>If you come across any unknown Eprints-specific issues please send a bug report to the eptech mailing list.<br />
[[Category:Debian and Ubuntu]]<br />
==Known Issues==<br />
<br />
===Wrong XML::LibXML Version===<br />
<br />
This affects mainly Ubuntu and older Debian distributions where the libxml package is too old. The package installer doesn't check the XML::LibXML version. Either install XML::LibXML 1.63 from cpan or disable it by setting enable_libxml to 0 in /usr/share/eprints3/perl_lib/EPrints/SystemSettings.pm.<br />
<br />
Installing 1.63 from cpan (as root):<br />
<br />
cpan XML::LibXML<br />
<br />
Alternatively you could follow the instructions at [[Installing_GDOME_on_Debian]] to install the GDOME XML library.<br />
<br />
Without either XML::LibXML or XML::GDOME Eprints uses a bundled XML::DOM implementation that has much lower performance and poorer Unicode support.<br />
<br />
Note that you can build Debian packages from CPAN modules using [http://packages.debian.org/dh-make-perl dh-make-perl] in order to keep track of those modules you've been building by yourself. Provided you've already configured your CPAN environment (that is, at least your proxies and servers), you can survive with:<br />
<br />
dh-make-perl --install --notest --cpan XML::LibXML<br />
<br />
===DiskSpace.pm measuring disk usage (reiserFS)===<br />
<br />
Not supported in the default package install, to add support add the following to the array defined in $EPRINTS_HOME/perl_lib/Filesys/DiskSpace.pm<br />
<br />
1448756819 => "REISERFS_SUPER_MAGIC", # 0x565A4653<br />
<br />
Many thanks to José Miguel Parrella Romero for pointing this out.<br />
<br />
Note that this was tested in a Debian GNU/Linux virtual private server running under Virtuozzo hypervision. Other filesystems, such as simfs, don't usually give any problems with DiskSpace.pm.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6023User:Ckeene/Ideas for future versions of eprints2008-04-19T08:39:37Z<p>Ckeene: /* One Repository, multiple views (long term?) */</p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!). <br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
== Enhance the eprint abstract page (a la flickr) ==<br />
the Eprints team briefly demonstrated this at OR08. It looked great.<br />
<br />
Basically two things:<br />
* At the moment many people come in via google, land on a page and that is it. If the Abstract page had 'see similar items' 'people who looked at this also looked at', plus tags etc for enhanced navigation. As well as these autogenerated facilities, perhaps something where repository managers can say 'if a record belongs to chemistry then advertise item x, or display this promotional image/text).<br />
* Something I know has been discussed is the idea that it is the item that is import. for documents, a large preview, for images and movies, they should be shown on the page. Again, I know people often refer to flick as a way of showing the content, with the metadata still visible but not dominant, and I would add my vote in saying this sounds like the right direction.<br />
<br />
== One Repository, multiple views (long term?) ==<br />
At the moment eprints has the model: One repository database has one user interface. <br />
<br />
I think there is scope in changing this to one repository, many interfaces. I include deposit/user area, branding, and certain config in with 'interface'. <br />
<br />
* Some Universities have created separate etheses repositories, surely it would be better if everything was in one database, but they were able to create a separate interface. So that theses would see a user area just for them, with unique branding, etc. Postgrad Office may want a unique deposit/management process for theses and not just the generic deposit process.<br />
* Some Universities have semi-autonomous units who have their own branding and organisation. These units may toy with a respository, but want to do it there way, with their deposit process, branding, a search just for their items. etc (but may be happy with the idea that their research shows up in the main repository as well. this would allow them to create a second interface to do accommodate them, rather than them creating their own repository.<br />
* Repository Managers go to departments to try and encourage them to make use of the IR. A Department may be interested, but again, want specific browse views and searches that can appear on their departmental pages, (they may, for example hate the idea of unpublished items showing up with published ones, or only want their items to show). The ability to say 'sure we can set that up' is a huge plus.<br />
<br />
Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6022User:Ckeene/Ideas for future versions of eprints2008-04-19T08:38:39Z<p>Ckeene: </p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!). <br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
== Enhance the eprint abstract page (a la flickr) ==<br />
the Eprints team briefly demonstrated this at OR08. It looked great.<br />
<br />
Basically two things:<br />
* At the moment many people come in via google, land on a page and that is it. If the Abstract page had 'see similar items' 'people who looked at this also looked at', plus tags etc for enhanced navigation. As well as these autogenerated facilities, perhaps something where repository managers can say 'if a record belongs to chemistry then advertise item x, or display this promotional image/text).<br />
* Something I know has been discussed is the idea that it is the item that is import. for documents, a large preview, for images and movies, they should be shown on the page. Again, I know people often refer to flick as a way of showing the content, with the metadata still visible but not dominant, and I would add my vote in saying this sounds like the right direction.<br />
<br />
== One Repository, multiple views (long term?) ==<br />
At the moment eprints has the model: One repository database has one user interface. <br />
<br />
I think there is scope in changing this to one repository, many interfaces. I include deposit/user area, branding, and certain config in with 'interface'. <br />
<br />
* Some Universities have created separate etheses repositories, surely it would be better if everything was in one database, but they were able to create a separate interface. So that theses would see a user area just for them, with unique branding, etc. Postgrad Office may want a unique deposit/management process for theses and not just the generic deposit process.<br />
* Some Universities have semi-autonomous units who have their own branding and organisation. These units may toy with a respository, but want to do it there way, with their deposit process, branding, a search just for their items. etc (but may be happy with the idea that their research shows up in the main repository as well. this would allow them to create a second interface to do accommodate them, rather than them creating their own repository.<br />
* Repository Managers go to departments to try and encourage them to make use of the IR. A Department may be interested, but again, want specific browse views and searchers that can appear on their departmental pages, (they may, for example hate the idea of unpublished items showing up with published ones, or only want their items to show). The ability to say 'sure we can set that up' is a huge plus.<br />
<br />
Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!<br />
<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6021User:Ckeene/Ideas for future versions of eprints2008-04-19T07:52:39Z<p>Ckeene: </p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!). <br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
== One Repository, multiple views (long term?) ==<br />
At the moment eprints has the model: One repository database has one user interface. <br />
<br />
I think there is scope in changing this to one repository, many interfaces. I include deposit/user area, branding, and certain config in with 'interface'. <br />
<br />
* Some Universities have created separate etheses repositories, surely it would be better if everything was in one database, but they were able to create a separate interface. So that theses would see a user area just for them, with unique branding, etc. Postgrad Office may want a unique deposit/management process for theses and not just the generic deposit process.<br />
* Some Universities have semi-autonomous units who have their own branding and organisation. These units may toy with a respository, but want to do it there way, with their deposit process, branding, a search just for their items. etc (but may be happy with the idea that their research shows up in the main repository as well. this would allow them to create a second interface to do accommodate them, rather than them creating their own repository.<br />
* Repository Managers go to departments to try and encourage them to make use of the IR. A Department may be interested, but again, want specific browse views and searchers that can appear on their departmental pages, (they may, for example hate the idea of unpublished items showing up with published ones, or only want their items to show). The ability to say 'sure we can set that up' is a huge plus.<br />
<br />
Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!<br />
<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Ideas_for_future_versions_of_eprints&diff=6020Ideas for future versions of eprints2008-04-19T07:30:54Z<p>Ckeene: Ideas for future versions of eprints moved to User:Ckeene/Ideas for future versions of eprints: I meant to put it in my user area!</p>
<hr />
<div>#REDIRECT [[User:Ckeene/Ideas for future versions of eprints]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6019User:Ckeene/Ideas for future versions of eprints2008-04-19T07:30:54Z<p>Ckeene: Ideas for future versions of eprints moved to User:Ckeene/Ideas for future versions of eprints: I meant to put it in my user area!</p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!). <br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6018User:Ckeene/Ideas for future versions of eprints2008-04-19T07:29:57Z<p>Ckeene: </p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!). <br />
<br />
== Enhance the concept of authors (and editors) ==<br />
<br />
Eprints has a type of person called a 'depositor'. they can log in, submit stuff, have a profile, list what they have submitted, etc. Nice.<br />
<br />
But Authors as a concept does not really exist. they are just bits on text strings in the system. Sure, we can generate a view of all authors (often so large and with variant entries that it is of limited use).<br />
<br />
Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.<br />
<br />
<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
== Refine search / facet search ==<br />
See an example on the left of [http://www.worldcat.org/search?qt=worldcat_org_all&q=sussex this worldcat page].<br />
<br />
On search results, allow people to refine by year, author, department, type, with-full text, published, peer review, etc.<br />
<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!<br />
<br />
== Things that have made it in to Eprints 3.1 ==<br />
=== Auto covert MS Word to PDF ===<br />
[April 08n update: this looks like it is a plugin in 3.1, excellent]<br />
<br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/Ideas_for_future_versions_of_eprints&diff=6017User:Ckeene/Ideas for future versions of eprints2008-04-19T07:07:38Z<p>Ckeene: New page: == Long term : fit in with academic workflow == Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. At the moment we 'bolt...</p>
<hr />
<div>== Long term : fit in with academic workflow ==<br />
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published.<br />
<br />
At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. <br />
<br />
This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).<br />
<br />
== Allow users to be authenticated by an external system ==<br />
<br />
See my [http://www.eprints.org/tech.php/8842.html email message from April 2008].<br />
<br />
At the moment eprints can be configured to use an LDAP server for authentication. Eprints takes the user credentials and then passes them to the LDAP server for authentication.<br />
<br />
Perhaps a more generic extension to this is to allow the our sourcing of authentication completely.<br />
<br />
E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.<br />
<br />
<br />
This is a little similar to what ezproxy can do<br />
http://www.oclc.org/us/en/support/documentation/ezproxy/usr/cgi.htm<br />
and also, in a way, to how shibboleth works.<br />
<br />
The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!). <br />
<br />
<br />
== Auto covert MS Word to PDF == <br />
The ability to let users upload a Word file and eprints to turn it in to a PDF (and store both) would make help many users and make the system more attractive to use.<br />
<br />
Telephone call..<br />
<br />
Humanities academic: "err hi, I've hear you're the people to contact to put my research online, how do I go about it?"<br />
<br />
eprints admin: "cool, you just need to find you final draft of your article, covert it to PDF, using any PDF tool such as Acrobat or PDFcreator, which you may need to install, if you have admin rights on your PC, and then...." [sounds of despair from other end of phone, caller hangs up]<br />
<br />
Of course, academics hardly ever phone up with such enthusiasm, but this talk of complicated stuff doesn't make it easy. If there's some sort of *nix library/tool out there which eprints could use to convert on the fly MS Word files to PDF, then this would make it so much easier from the researcher's point of view.<br />
They just need to upload their Word file, and it's made available as a PDF to users.<br />
<br />
<br />
== Auto LOC classify ==<br />
<br />
Eprints has a simple LOC based classification system setup by default. This is good, but researchers don't find LOC that easy to decide which category to use, and find it all a little complex.<br />
<br />
If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).<br />
<br />
<br />
== Auto submit to other repositories ==<br />
<br />
"why should I deposit in the IR when I have arxiv.org where all my peers submit to as well?"<br />
"If I have to deposit to my Research Councils repository* why should I deposit to the IR as well?"<br />
<br />
* http://www.sparceurope.org/press_release/RC%20OA%20policies%20v1.3.xls<br />
<br />
Good questions! and what if the answer was "By submitting to the IR it will automatically be uploaded to the other repository just by ticking a box"<br />
<br />
With SWORD this should now finally be possible. This could be a killer feature and I think it could do more than just support the protocol. It should use logic to recommend other repositories that the user can just tick for it to try and submit the item to as well i.e. if user is a physicist suggest arXiv, or if item has been categorized as 'Econmics' then suggest [http://repec.org/ repec], or if it has a co-author at Watford Gap University then suggest that it is deposited their as well.<br />
<br />
<br />
== Make document available in other formats ==<br />
<br />
Similar in a way to the first idea. If someone deposits a PDF/PS/RTF then make it available in a number of file types, either converting it on the fly or perhaps converting it as it is deposited (use more space, but may have archival plus points'.<br />
<br />
<br />
These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)<br />
Like I say, these are all non-trivial, but hope it makes for good food for thought!</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene&diff=6016User:Ckeene2008-04-19T06:44:54Z<p>Ckeene: </p>
<hr />
<div>[[Ideas for future versions of eprints]]<br />
== Chris Keene ==<br />
Chris Keene. <br />
Technical Development Manager, <br />
University of Sussex Library, <br />
UK.<br />
http://www.sussex.ac.uk/library/<br />
<br />
== Eprints 3 upgrade ==<br />
I'm keeping a journal of our upgrade/migration from eprints2 to '''eprints3''': [[User:Ckeene/ep3_upgrade]]<br />
<br />
== Stuff I've done related to eprints ==<br />
# I manage http://eprints.sussex.ac.uk for the University of Sussex <br />
# We have some background information http://www.sussex.ac.uk/library/ir/<br />
# and a not very much updated news/blog http://researchonline.lib.sussex.ac.uk/<br />
# I have made available some very simple analog config files and perl scripts for producing web usage statistics: [[Files/Simple_usage_statistics_(using_analog)]]<br />
# I made a tiny change to [[Files/Import_BibTeX_via_CGI]] to fix a bug<br />
# When working on something which is new to me related to eprints, I try to update the wiki to expand on anything unclear or missing. [[Special:Contributions/Ckeene]]<br />
<br />
== misc ==<br />
A Test:<br />
[[User:Ckeene/page2]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene&diff=6015User:Ckeene2008-04-19T06:44:43Z<p>Ckeene: </p>
<hr />
<div>[Ideas for future versions of eprints]<br />
== Chris Keene ==<br />
Chris Keene. <br />
Technical Development Manager, <br />
University of Sussex Library, <br />
UK.<br />
http://www.sussex.ac.uk/library/<br />
<br />
== Eprints 3 upgrade ==<br />
I'm keeping a journal of our upgrade/migration from eprints2 to '''eprints3''': [[User:Ckeene/ep3_upgrade]]<br />
<br />
== Stuff I've done related to eprints ==<br />
# I manage http://eprints.sussex.ac.uk for the University of Sussex <br />
# We have some background information http://www.sussex.ac.uk/library/ir/<br />
# and a not very much updated news/blog http://researchonline.lib.sussex.ac.uk/<br />
# I have made available some very simple analog config files and perl scripts for producing web usage statistics: [[Files/Simple_usage_statistics_(using_analog)]]<br />
# I made a tiny change to [[Files/Import_BibTeX_via_CGI]] to fix a bug<br />
# When working on something which is new to me related to eprints, I try to update the wiki to expand on anything unclear or missing. [[Special:Contributions/Ckeene]]<br />
<br />
== misc ==<br />
A Test:<br />
[[User:Ckeene/page2]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_3_on_Debian&diff=5777Installing EPrints 3 on Debian2007-10-18T15:53:04Z<p>Ckeene: See also: Installing EPrints 3 via apt (Debian/Ubuntu)</p>
<hr />
<div>{{Installation}}<br />
<br />
See also: [[Installing EPrints 3 via apt (Debian/Ubuntu)]]<br />
<br />
== Setting up Debain ==<br />
<br />
This instructions assume a working Debian ("Edgy Eft") installation (or close approximation thereof).<br />
<br />
== Install EPrints Dependencies ==<br />
<br />
<br />
Install Apache and mod_perl:<br />
<br />
root@debian$ apt-get install apach2-mpm-prefork libapache2-mod-perl2<br />
<br />
Install MySQL:<br />
<br />
root@debian$ apt-get install install mysql-server<br />
<br />
Install perl dependencies:<br />
<br />
root@debian$ apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl libxml-parser-perl.<br />
<br />
== Auxiliary Packages ==<br />
<br />
You need further packages for the seamless work of Eprints; these might or might not be installed on the system:<br />
<br />
Packages for building eprints:<br />
<br />
root@debian$ apt-get install gzip tar unzip make lynx wget ncftp ftp<br />
<br />
Programs for extracting content:<br />
<br />
root@debian$ apt-get install gs xpdf xv antiword elinks<br />
<br />
Programs making pictures, formulas, etc.<br />
<br />
root@debian$ apt-get install pdftk tetex-bin psutils imagemagick<br />
<br />
== Configuring MySQL ==<br />
<br />
It is strongly recommended that you set a root password in mysql:<br />
<br />
$ mysqladmin -u root password <new password><br />
<br />
== Create an 'eprints' system user ==<br />
root@debain$ adduser --system --home /opt/eprints3 --group eprints <br />
<br />
Add the 'www-data' user to the 'eprints' group:<br />
<br />
root@debain$ adduser www-data eprints<br />
<br />
== Install EPrints ==<br />
<br />
Download EPrints 3. Unpack and install the tarball:<br />
<br />
$ tar xzvf eprints-3.x.y.tar.gz<br />
$ cd eprints-3.x.y<br />
$ ./configure --with-smtp-server=smtp.yourdomain<br />
$ sudo ./install.pl<br />
<br />
== Set up Apache2 ==<br />
<br />
Add this line to <tt>/etc/apache2/sites-available/eprints</tt><br />
Include /opt/eprints3/cfg/apache.conf<br />
and enable the site<br />
$ sudo a2ensite eprints<br />
(this leaves <tt>/etc/apache2/apache.conf</tt> untouched, making future Apache upgrades easier)<br />
<br />
== Set up the indexer as a service ==<br />
<br />
$ sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
<br />
Make the indexer start automatically when the machine is rebooted:<br />
<br />
$ sudo update-rc.d epindexer defaults 99 99<br />
<br />
== Configure an archive ==<br />
<br />
Follow the steps in the main EPrints documentation to configure an archive.<br />
* [[Getting Started with EPrints 3]]<br />
<br />
== Restarting Apache ==<br />
<br />
$ sudo /etc/init.d/apache2 force-reload</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Talk:Manual&diff=5776Talk:Manual2007-10-18T15:50:01Z<p>Ckeene: 3 columns</p>
<hr />
<div>Manual todo list...<br />
<br />
(make sure pages are linked in from [[Documentation]] after they are completed)<br />
<br />
These pages need either creating, updating, or gutting of information to make new pages.<br />
<br />
== moj ==<br />
* Screenshots for metadata (render, input, search)<br />
* Explain XML import/export (format + howto) - normal fields, multiple fields, compound fields, name fields, documents, files<br />
* Per metadata field: db cols, phrases (use boolean as guide, 'none' if n/a)<br />
<br />
== tmb ==<br />
<br />
* [[Contact]]<br />
* [[Installation]]<br />
* [[Getting Started]]<br />
* [[Entire_Manual]] -- do we want this?<br />
* [[Organisation_Hierarchy]] - update for EPrints 3<br />
* add sections on how to perform specific tasks.<br />
** update template<br />
** remove eprint type<br />
** add eprint type<br />
** ditto for users.<br />
** add field<br />
** remove field <br />
** etc.<br />
* This should be updated and part of the manual: [[Branding/Logos]]<br />
* [[HTTPS]] - not sure of how well 3.0 works with https - easiest to https the whole thing (shouldn't be _too_ hard...)<br />
* [[Troubleshooting]] - any of this still relevant? Maybe move it to TroubleshootingV2 page?<br />
<br />
== cjg ==<br />
* update [[Metadata]]<br />
* [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/cfg.d]]<br />
* [[Structure]]<br />
* [[Repository_configuration]] (get anything useful out of it)<br />
* [[EPrints_configuration]] (get useful stuff out of it)<br />
* [[perl_lib/EPrints/SystemSettings.pm]]<br />
* [[EPrint Object]] etc.<br />
<br />
== 3 columns ==<br />
<br />
the 3 columns doesn't look so good when you don't have your browser full screen.<br />
<br />
I wonder whether it would be better going to two columns (or even 1)?<br />
<br />
[[User:Ckeene|Ckeene]] 16:50, 18 October 2007 (BST)</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=HTTPS&diff=5232HTTPS2007-08-24T10:35:06Z<p>Ckeene: remove spam</p>
<hr />
<div>#REDIRECT [[How to use EPrints with HTTPS]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Category:Installation&diff=5231Category:Installation2007-08-24T10:34:10Z<p>Ckeene: remove spam</p>
<hr />
<div>The default installation of EPrints is on a stand-alone linux system, but this is not the only way EPrints can (and has) been installed.<br />
<br />
Here are some other ways:<br />
<br />
* [[non-root_proxy|Proxied to a non-root]] user account: Where the server and all associated code is installed without root/admin access to anything<br />
* [[How to set up EPrints on virtual directories other than root|Hosted on virtual directories other than root]] - sharing with other Web applications on the same server</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Organisation_Hierarchy&diff=5230Organisation Hierarchy2007-08-24T10:32:51Z<p>Ckeene: remove spam</p>
<hr />
<div>{{development}}<br />
{{manual}}<br />
<br />
all the files I discuss are in /opt/eprints2/archives/YOURID/cfg/<br />
<br />
<br />
<br />
1.<br />
modify subjects to add your new tree, with a top level with the id "groups" and it's parent set to be "ROOT" (similar to the subjects node). This is the top node of your new subjects tree.<br />
<br />
2.<br />
add the new field to eprints objects (ArchiveMetadataFieldsConfig.pm):<br />
{ name => "groups", type=>"subject", top=>"groups", multiple => 1,<br />
browse_link => "groups",<br />
render_input=>\&EPrints::Extras::subject_browser_input },<br />
<br />
for reference, that all means<br />
name = id of the field<br />
type = type (heirarchical subject)<br />
multiple = you can select more than one value at once<br />
top = the top node in the tree<br />
render_input = use the clever subject input, rather than just a big pull-down menu<br />
browse_link = link values in this to pages in /view/groups/ (which we'll make in a minute)<br />
<br />
Now run erase_archive & create_tables (assuming you've no live data, otherwise it's a bit harder). You may also need to run import_subjects and the other scripts mentioned in the [[http://www.eprints.org/documentation/tech/php/installation.php#creating_the_database_tables_and_website_ 'creating an archive']] documentation.<br />
<br />
3.<br />
add a human readable description for it:<br />
edit phrases-en.xml<br />
<ep:phrase ref="eprint_fieldname_groups">Groups</ep:phrase><br />
<ep:phrase ref="eprint_fieldhelp_groups">add some relevant help for selecting groups here!</ep:phrase><br />
<ep:phrase ref="metapage_title_groups">Groups</ep:phrase><br />
<ep:phrase ref="viewname_eprint_groups">Groups</ep:phrase><br />
<br />
(the 3rd one is the title for the page on the input form, also called "groups", the 4th is the name which appears on the /view/ pages)<br />
<br />
4.<br />
add the field to each type of eprint<br />
edit metadata-types.xml<br />
each time you find<br />
<br />
<page name="subjects" /><br />
<field name="subjects" required="yes" /><br />
<br />
<br />
add below or before, which ever you prefer,<br />
<br />
<page name="groups" /><br />
<field name="groups" required="yes" /><br />
<br />
5.<br />
add it to the "abstract" pages:<br />
edit ArchiveRenderConfig.pm<br />
find:<br />
<br />
# Subjects...<br />
$table->appendChild( _render_row(<br />
$session,<br />
$session->html_phrase( "eprint_fieldname_subjects" ),<br />
$eprint->render_value( "subjects" ) ) );<br />
<br />
<br />
add below or above or nearby:<br />
<br />
<br />
# Groups...<br />
$table->appendChild( _render_row(<br />
$session,<br />
$session->html_phrase( "eprint_fieldname_groups" ),<br />
$eprint->render_value( "groups" ) ) );<br />
<br />
6.<br />
add it to the browse /view/ section:<br />
Edit ArchiveConfig.pm<br />
Add:<br />
{ id=>"groups", fields=>"groups", order=>"-date_effective/title", hideempty=>1 }</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Files/EPrints_3.0_Beta_2&diff=5229Files/EPrints 3.0 Beta 22007-08-24T10:31:56Z<p>Ckeene: remove spam</p>
<hr />
<div>= EPrints 3.0 2nd Beta Release =<br />
<br />
Released 14th November 2006.<br />
<br />
== Download ==<br />
<br />
http://files.eprints.org/120/<br />
<br />
== Requires ==<br />
* Apache 2 (avoid 2.2.2)<br />
* mod_perl 2<br />
* Perl<br />
* Some perl modules<br />
* UNIX like operating system<br />
<br />
== Release Notes ==<br />
<br />
EPrints 3 does not need to be the same user as the webserver, but it does need to be a user which is in the same UNIX group.<br />
<br />
If there is any bug which is a showstopper, let us know and we'll try and get another beta out ASAP.<br />
<br />
DO NOT try to install over the top of EPrints 2, it will just make a mess!<br />
<br />
There is currently '''no way''' to upgrade from 2.3 to 3.0 but that will be a side development project over the next few months, released sometime after, or maybe even before, 3.0 in January.<br />
<br />
To get started run "epadmin" this has taken over many of the other scripts (create tables, erase archives, create user etc.)<br />
<br />
== Bugs == <br />
<br />
Feedback and bug reports may be sent to cjg@ecs.soton.ac.uk (The Lead Developer). I suggest that an initial bug report is kept quite short as we already have a big list. If I don't already know about it, I'll ask for more info.<br />
<br />
== Things added since beta 1 ==<br />
* Redesigned search forms.<br />
* Added experimental support for XML::LibXML.<br />
* Basic autocomplete now works on creators and journals<br />
* Using the progress bar to jump stages now saves current changes.<br />
* OpenURL resolver.<br />
* Improved interface for file upload screen.<br />
* Improved interface for subject stage.<br />
* Added "Add User" administration screen.<br />
* Redesigned user interface for Items and Review screens.<br />
* Fixed bug which prevented EP3 working with Apache >= v2.2.2<br />
* Added <link>'s to alternate versions in head of search results and item summary pages.<br />
* Redesigned document security configuration to be easier to understand.<br />
* Improved the reject/remove notification screens and emails.<br />
* Added staff search screens for eprints, users and history.<br />
* Other bugfixes.<br />
* Other user interface improvements.<br />
<br />
== Things planned for Release Candidate 1 ==<br />
<br />
This is a list of things we plan to add which aren't in beta-1:<br />
<br />
This does not include the many minor user interface tweaks on our list, or bugs.<br />
<br />
* Subject Add/Edit<br />
* A way to control the reply-to address of email<br />
* Clone EPrint<br />
* Use EPrint as Template<br />
* epadmin will absorb even more bin/ scripts<br />
<br />
EPrints 3 logs all hits on documents and abstracts but does not yet do anything smart with that data. We're working on that as a separate project.<br />
<br />
== Upgrading from EPrints 3.0 beta 1 ==<br />
<br />
If you already have a repository set up with beta-1 you need to do the following:<br />
<br />
=== Essential things to do (per repository) after 3.0 beta-1 to 3.0 beta-2 upgrade ===<br />
<br />
* The database has changed a tiny bit so run<br />
bin/epadmin upgrade ARCHIVEID<br />
<br />
* edit cfg.d/user_fields_default.pl and add these rows inside the sub:<br />
<br />
$data->{items_fields} = [ "lastmod", "title", "type", "eprint_status" ];<br />
$data->{review_fields} = [ "status_changed", "title", "type", "userid" ];<br />
<br />
* Any existing users will not have these preferences set, so they will need to modify their profile to set this. These fields control what fields you see on the Items and Review pages.<br />
<br />
* security.pl has been rewritten. Replace your copy (after you upgrade) with the one from /opt/eprints3/lib/defaultcfg/cfg.d/security.pl<br />
<br />
* Do the same for search.pl<br />
<br />
=== Recommended but not essential ===<br />
<br />
* Do the same for eprint_render.pl as for security.pl and search.pl - the new version adds links in the summary page to the various versions of the metadata available, and tweaks some other stuff.<br />
<br />
* We've changed the default template a bit. You may wish to replace your cfg/lang/en/templates/default.xml and cfg/cfg.d/dynamic_template.pl with the versions from lib/defaultcfg/<br />
<br />
== Plugins ==<br />
<br />
You may notice the powerful new plugin system for EPrints 3. If you're interested in writing a plugin, get in touch! Or just upload them to files.eprints.org<br />
<br />
If there's a plugin you really need and don't have the time or skills to write yourself, why not hire [http://eprints.org/services EPrints Services] to write it for you!</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Talk:How_to_use_EPrints_with_HTTPS&diff=5224Talk:How to use EPrints with HTTPS2007-08-24T10:28:11Z<p>Ckeene: remove spam</p>
<hr />
<div></div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4803User:Ckeene/ep3 upgrade2007-08-15T10:29:58Z<p>Ckeene: /* Thumbnails */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks they are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.<br />
# generate_abstracts<br />
# move mouse over a pdf icon in the web interface, thumbnail appears! it now works.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4787User:Ckeene/ep3 upgrade2007-08-14T14:24:47Z<p>Ckeene: /* Thumbnails */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks there are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.<br />
# generate_abstracts<br />
# move mouse over a pdf icon in the web interface, thumbnail appears! it now works.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4786User:Ckeene/ep3 upgrade2007-08-14T14:03:13Z<p>Ckeene: /* Ubuntu / system packages Part 2 */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED: mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks there are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4785User:Ckeene/ep3 upgrade2007-08-14T14:02:26Z<p>Ckeene: </p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED:<br />
mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks<br />
<br />
<br />
== Back to migration ==<br />
<br />
=== Thumbnails ===<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
# error message still appearing ("Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73"<br />
# find email message: http://www.eprints.org/tech.php/6484.html<br />
# this points to /opt/eprints3/perl_lib/EPrints/systemSettings.pm<br />
# this contains lines such as "'convert' => 'NOTFOUND'"<br />
#* so even though convert - and others - are now installed eprints thinks there are not<br />
#* I can either manually edit this file or rerun the installer.<br />
#* I'll try reinstalling, useful for future reference.<br />
# cd /home/eprints/eprints-3.0.2-beta-3<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# ./install<br />
#* oddly the systemsettings file is still showing the same<br />
#* after renaming the file and running ./configure, ./install.pl again systemsettings.pm now shows the locations and paths for the executables!<br />
# stop start eprints<br />
# /opt/eprints3/bin/epadmin redo_thumbnails ep3m<br />
#* various warning messages as it finds problems with PDF files but these can probably be ignored.</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4776User:Ckeene/ep3 upgrade2007-08-14T11:22:46Z<p>Ckeene: /* First attempt to migrate data */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).<br />
# sudo /etc/init.d/epindexer<br />
# generate_views etc<br />
<br />
This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!<br />
<br />
Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required. <br />
<br />
== Ubuntu / system packages Part 2 ==<br />
Since I started this process (which has come in very small bursts with big gaps in-between) it looks like http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10 has been updated. Excellent, looks like it is recommending some packages which I will install now.<br />
# http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo aptitude install pdftk tetex-bin psutils imagemagick<br />
#* oddly this results in the British version of firefox being uninstalled!<br />
#* The following packages are unused and will be REMOVED:<br />
mozilla-firefox-locale-en-gb<br />
# sudo aptitude install gs xpdf xv antiword elinks</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4774User:Ckeene/ep3 upgrade2007-08-14T10:57:03Z<p>Ckeene: /* First attempt to migrate data */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: <br />
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
#* I suspect these should be ok<br />
#* note http://www.eprints.org/tech.php/7265.html<br />
# use ubuntu package manager to install imagemagick<br />
# sudo /usr/sbin/apache2ctl stop<br />
# sudo /usr/sbin/apache2ctl start<br />
# /opt/eprints3/bin/epadmin erase_eprints ep3m<br />
#* this did not resolve the issue (though /usr/bin/convert exists).</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4773User:Ckeene/ep3 upgrade2007-08-14T09:18:27Z<p>Ckeene: /* First attempt to migrate data */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?<br />
# cd migration/mtoolkit<br />
# ./export3data.pl sussex eprints > eprints.xml<br />
# ./export3data.pl sussex users > users.xml<br />
# ./export3data.pl sussex subjects > subjects.xml<br />
# /opt/eprints3/bin/epadmin erase_data ep3m <br />
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml<br />
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml<br />
# a number of warnings appear: Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.<br />
# * I suspect these should be ok<br />
# * note http://www.eprints.org/tech.php/7265.html</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4772User:Ckeene/ep3 upgrade2007-08-14T08:09:55Z<p>Ckeene: /* First attempt to migrate data */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
== First attempt to migrate data ==<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
## follow creation process (db bit works fine this time, but requires a decent password!).<br />
# started to follow http://wiki.eprints.org/w/Migration<br />
# downloaded and extracted toolkit<br />
# run mkconfig.pl sussex<br />
# cd /opt/eprints3/archives/ep3m<br />
# cp -rp cfg cfg.orig<br />
# copy cfg from toolkit to ep3m<br />
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. <br />
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4770User:Ckeene/ep3 upgrade2007-08-13T17:53:34Z<p>Ckeene: create First attempt to migrate data</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007<br />
<br />
<br />
=== First attempt to migrate data ===<br />
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)<br />
# create new archive:<br />
## /opt/eprints3<br />
## bin/epadmin create<br />
##</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4468User:Ckeene/ep3 upgrade2007-06-22T16:55:22Z<p>Ckeene: /* Configure an archive */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!<br />
# http://ep3v.lib.sussex.ac.uk:8082/<br />
<br />
22 June 2007</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4467User:Ckeene/ep3 upgrade2007-06-22T16:33:04Z<p>Ckeene: /* The plan */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3v) - v for vanilla<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors)<br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4466User:Ckeene/ep3 upgrade2007-06-22T16:31:50Z<p>Ckeene: /* Configure an archive */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3a)<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors) <br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here. I also found the bottom of [[Installing EPrints 3 on RedHat Enterprise 4]] useful. (I've updated the Ubuntu page to link to these two pages).<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# epadmin create, again, good until, complains "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db (which I should have done when I deleted the directory). <br />
# because the create process terminated prematurely I need to run some commands manually<br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
# bin/generate_static ep3v<br />
# bin/import_subjects ep3v<br />
# bin/generate_apacheconf<br />
# sudo /usr/sbin/apache2ctl stop<br />
# It works!</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4464User:Ckeene/ep3 upgrade2007-06-22T16:16:55Z<p>Ckeene: /* Eprints 3 install */</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3a)<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors) <br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl<br />
<br />
=== Apache setup ===<br />
# sudo vi /etc/apache2/sites-available/eprints<br />
# add to this new file: Include /opt/eprints3/cfg/apache.conf<br />
# sudo a2ensite eprints<br />
<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# but: "ln: creating symbolic link `/etc/init.d/epindexer' to `/opt/eprints3/bin/epindexer': File exists"<br />
# looks like it will overwrite the eprints 2 indexer: ls -l shows... /etc/init.d/epindexer -> /opt/eprints2/bin/epindexer But this is ok, we run the indexer as a job from cron "/opt/eprints2/bin/indexer start --rollcount 6 --once" and don't use this symlink, which is for running it as a service, should be ok to overwrite (I hope)...<br />
# sudo rm /etc/init.d/epindexer<br />
# sudo ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer<br />
# sudo update-rc.d epindexer defaults 99 99 : produced an error message that it already existed, so should be fine to skip this.<br />
<br />
<br />
=== Configure an archive ===<br />
# Documentation a little unclear here, the Ubuntu docs tell us to follow the 'main eprints3 documentation', so from the main Eprints3 page I clicked on 'installation' and then followed [[Getting Started]] on the right, this seems half updated for eprints3 but also referes to eprints2. <br />
# However I also found on the main Eprints 3 docs page a link to [[Getting Started with EPrints 3]] which I shall follow here.<br />
# cd /opt/eprints3/<br />
# bin/epadmin create<br />
# (at this point I create a cname in our dns for ep3v.lib.sussex.ac.uk as an alias for eprints.lib.sussex.ac.uk, the v is for vanilla as this will be a eprints3 install with no changes made to it for reference)<br />
# archiveID is ep3v<br />
# continue to enter details as prompted, at db username i accept the default it suggests. Get stuck with db password, reports 'bad input'. I quit out of this, and then played with epadmin config_db. In the end had a database but no user and it just didn't seem happy. Easy option, delete directory and start again!<br />
# This time now problems, well it did still complain "EPrints can create the database, and grant the correct permissions." when doing the db stuff, this was because I had forgotten to delete the ep3v db as well. <br />
# run bin/epadmin config_db ep3v<br />
# run bin/create_user ep3v (seems to have a fairly strict password criteria, a 7 digit combination of numbers and letters produced 'bad input')<br />
#</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene/ep3_upgrade&diff=4463User:Ckeene/ep3 upgrade2007-06-22T14:04:33Z<p>Ckeene: Eprints 3 install</p>
<hr />
<div>== Eprints 3 upgrade ==<br />
<br />
A journal of our upgrade process from eprints2 to eprints3. This will include my own stupid mistakes and errors, many will be laughable and show my true incompetence. I keep them here so others do not do the same!<br />
<br />
==== Current situation ====<br />
Current Version: EPrints 2.3.12 (Southern Chicken) [Born on 2005-05-24]<br />
Running on Ubuntu 6.06 LTS (based on Debian)<br />
Visual look and quite a bit of the wording has been changed, and endnote/BibTeX import functionality has been added (via the downloads from the eprints.org site).<br />
<br />
<br />
<br />
=== The plan ===<br />
# Apache 2 installed, with mod perl and php<br />
# Other dependencies<br />
# Install eprints3<br />
# Create test archive (ep3a)<br />
# Install and run migration tool. Document results. <br />
# Look in to problems, use mailing list for support<br />
# Modify wording of user interface (both for depositors and end users) to follow changes made on eprints2 (where they still apply and where changes were not bought across)<br />
# Apply Sussex Templates to eprints3<br />
# Install additional modules to bring in line with extra functionality of our eprints2 setup, see table below<br />
#Repeat migration process of data to test and address issues.<br />
# Follow steps to add additional functionality, such as auto-complete features, which are not out-of-the-box, but core features of eprints3.<br />
# Update documentation and screenshots ready for eprints3<br />
# Demonstrate to others, solicit feedback<br />
# Make changes based on user feedback<br />
# Migrate data one final time, update apache so that eprints.sussex.ac.uk points to eprints3, not eprints2. This will make eprints3 live. woohoo!<br />
<br />
Steps to bring eprint3 (out of the box) in-line with our current eprints2<br />
# Import from Endnote <br />
# Import from Bibtex <br />
# LDAP authentication <br />
# Import/update users from text file <br />
# Fields created to hold record id (from Uni pub db) and personnel id (for Sussex authors) <br />
<br />
== Install Apache 2, mod_perl, etc ==<br />
# key doc http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# sudo apt-get install apache2 libapache2-mod-perl2<br />
# eprints2 is on port 80. vi /etc/apache2/ports.cfg, changed from 80 to 8082<br />
# /usr/sbin/apache2ctl start<br />
# http://localhost:8082/ http://researchonline.lib.sussex.ac.uk:8082/ http://eprints.sussex.ac.uk:8082/ all work!<br />
# [we already have mysql installed - skip step]<br />
# sudo apt-get install libxml-libxml-perl libunicode-string-perl \<br />
libterm-readkey-perl libmime-lite-perl libdbd-mysql-perl<br />
# most of these were already installed. but at least<br />
libterm-readkey-perl libmime-lite-perl<br />
were not.<br />
# /etc/init.d/httpd stop start - eprints2 is still working!<br />
# sudo cpan install Readonly<br />
<br />
== Eprints 3 install ==<br />
# Follow http://wiki.eprints.org/w/Installing_EPrints_3_on_Ubuntu_6.10<br />
# We already have an 'eprints' user so I'm going to try and not create one now, the only issue might be that the instructions state the users home should be /opt/eprints3 but I'm going to leave it as /home/eprints/ and see what happens<br />
# sudo adduser www-data eprints<br />
# tar xzvf eprints-3.0.2-beta-3.tar.gz (yup I'm installing a beta!)<br />
# cd eprints-3.0.2-beta-3<br />
# Remind myself of our smtp server: grep smtp /opt/eprints2/perl_lib/EPrints/SystemSettings.pm<br />
# ./configure --with-smtp-server=smtp.sussex.ac.uk<br />
# sudo ./install.pl</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=Manual&diff=4454Manual2007-06-19T11:18:48Z<p>Ckeene: /* Installing EPrints & Getting Started */ added Installing EPrints 3 on Ubuntu 6.10</p>
<hr />
<div>See the [[Main Page]] for other areas of this wiki.<br />
__NOTOC__<br />
= Introduction =<br />
<br />
* [[Introduction]]<br />
* How to Get Help/Support<br />
* [[History]] <br />
<br />
= Installing EPrints & Getting Started =<br />
<br />
* [[Required software]]<br />
* [[Installation|Installing EPrints]]<br />
** [[Recommended Platforms]]<br />
** [[Installing Eprints 3 on Fedora Core 6]]<br />
** [[Installing EPrints 3 on RedHat Enterprise 4]]<br />
** [[Installing EPrints 3 on OS X]]<br />
** [[Installing EPrints 3 on Ubuntu 6.10]]<br />
** ''[[:Category:Installation|other platforms]]''<br />
* [[Upgrading EPrints 3 versions]]<br />
* [[Migration|Migrating from EPrints 2.3]]<br />
* [[Getting Started with EPrints 3|Getting Started]]<br />
* [[Backups]]<br />
* [[Troubleshooting]]<br />
* Advanced Installation<br />
** [[Https3]]<br />
* [[:Category:Installation|Installing]] EPrints on various platforms.<br />
<br />
= How-to Guides =<br />
<br />
''[http://en.wikipedia.org/wiki/Howto What is a how-to?]<br />
<br />
* Orientation <span style="color: #f94; font-size: 130%">(Start here)</span><br />
** [[Configuration orientation|New to EPrints 3?]] - ''before diving into the how-tos, take some time to read through this brief orientation guide and familiarise yourself with the EPrints configuration landscape...''<br />
** [[EPrints_3_Configuration_orientation_for_EPrints_2_administrators|Migrated from EPrints 2?]] - ''this orientation guide is intended to help you re-orient yourselves in your new EPrints 3 set up...'' <br />
* [[Branding with confidence]] - ''one of the most common EPrints customisations is to add your own institution's branding and "look and feel" to the interface...''<br />
** [[Branding, the next level]] - ''how to completely change the interface to your own design''<br />
* [[Adding new views]]<br />
* Workflow<br />
* Deposit Types<br />
** [[Removing types]]<br />
* Metadata<br />
* Subjects (fold in with Organisation Hierarchy under "controled vocabularies")<br />
* [[EPrints_3_Organisation_Hierarchy|Organisation Hierarchy]] - ''how to put your own organisation's Hierarchy into EPrints 3''<br />
* Searches<br />
* [[Autocompletion and Authority Files (Romeo Autocomplete)]] - ''add autocomplete functionality to the Publication Title input field based on an authority file downloaded from EPrints Romeo...''<br />
* [[Create Export Plugins]] - ''create a Perl Module that will export your data...''<br />
* [[Login-Only Repository]] - ''require a username and password to access all pages (including search, browse, and the front page)...''<br />
* [[Change Deposit Status in Bulk]] - ''move a large number of deposits from inbox to archive<br />
* [[Customisation|more]]<br />
<br />
= Misc =<br />
<br />
* [[Preservation Support]] in GNU EPrints 3<br />
* I18n<br />
* [[How to contribute]]<br />
** [[Extension Packages]]<br />
<br />
= Technical Reference =<br />
<br />
* [[EPrints Directory Structure]] - will be linked somewhere better, later.<br />
<br />
* [[Metadata]] - configuring metadata fields.<br />
* [[Archives/ARCHIVEID/cfg/|Repository Configuration]]<br />
* [[XML Configuration]] Files<br />
** [[EPScript]] - documentation for the EP3 Scripting language (for use in citations and workflow files).<br />
** [[EPrints Control Format]] - the structure used to embed EPScript in an XML configuration file.<br />
** [[Citation Format]]<br />
** [[Workflow Format]] - the structure of the EP3 workflow files<br />
** [[Phrase Format]]<br />
** [[Template Format]]<br />
** [[XPAGE Format]]<br />
* [[XML Export Format]]<br />
* EPrints data structure <br />
** of the software<br />
** of the database (relating the dataobjects to each other using eprints fields)<br />
* [[Data Object]]s and data sets<br />
** The [[EPrint Object]]<br />
** The [[User Object]]<br />
** The [[Document Object]]<br />
** The [[Subject Object]]<br />
** The [[Saved Search Object]]<br />
** The [[History Object]]<br />
** The [[Access Object]]<br />
** The [[Request Object]]<br />
* Plugins<br />
** Import<br />
** [[Export Plugins]]<br />
** Components<br />
** Screen<br />
** Convert<br />
* [[Autocompletion]]<br />
** [[Understanding IDs in Workflow Forms]]<br />
* [[API]]<br />
* [[Dynamic Template System]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene&diff=4453User:Ckeene2007-06-19T11:12:27Z<p>Ckeene: </p>
<hr />
<div>== Chris Keene ==<br />
Chris Keene. <br />
Technical Development Manager, <br />
University of Sussex Library, <br />
UK.<br />
http://www.sussex.ac.uk/library/<br />
<br />
== Eprints 3 upgrade ==<br />
I'm keeping a journal of our upgrade/migration from eprints2 to '''eprints3''': [[User:Ckeene/ep3_upgrade]]<br />
<br />
== Stuff I've done related to eprints ==<br />
# I manage http://eprints.sussex.ac.uk for the University of Sussex <br />
# We have some background information http://www.sussex.ac.uk/library/ir/<br />
# and a not very much updated news/blog http://researchonline.lib.sussex.ac.uk/<br />
# I have made available some very simple analog config files and perl scripts for producing web usage statistics: [[Files/Simple_usage_statistics_(using_analog)]]<br />
# I made a tiny change to [[Files/Import_BibTeX_via_CGI]] to fix a bug<br />
# When working on something which is new to me related to eprints, I try to update the wiki to expand on anything unclear or missing. [[Special:Contributions/Ckeene]]<br />
<br />
== misc ==<br />
A Test:<br />
[[User:Ckeene/page2]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene&diff=4452User:Ckeene2007-06-19T11:11:03Z<p>Ckeene: </p>
<hr />
<div>== Chris Keene ==<br />
Chris Keene. <br />
Technical Development Manager, <br />
University of Sussex Library, <br />
UK.<br />
http://www.sussex.ac.uk/library/<br />
<br />
== Eprints 3 upgrade ==<br />
I'm keeping a journal of our upgrade/migration from eprints2 to '''eprints3''': [[User:Ckeene/ep3_upgrade]]<br />
<br />
== Stuff I've done related to eprints ==<br />
# I manage http://eprints.sussex.ac.uk for the University of Sussex <br />
# We have some background information http://www.sussex.ac.uk/library/ir/<br />
# and a not very much updated news/blog http://researchonline.lib.sussex.ac.uk/<br />
# I have made available some very simple analog config files and perl scripts for producing web usage statistics: [[Files/Simple_usage_statistics_(using_analog)]]<br />
# I made a tiny change to [[Files/Import_BibTeX_via_CGI]] to fix a bug<br />
# When working on something which is new to me related to eprints, I try to update the wiki to expand on anything unclear or missing.<br />
<br />
== misc ==<br />
A Test:<br />
[[User:Ckeene/page2]]</div>Ckeenehttps://wiki.eprints.org/w/index.php?title=User:Ckeene&diff=4451User:Ckeene2007-06-19T11:07:38Z<p>Ckeene: </p>
<hr />
<div>== Chris Keene ==<br />
Chris Keene. <br />
Technical Development Manager, <br />
University of Sussex Library, <br />
UK.<br />
http://www.sussex.ac.uk/library/<br />
<br />
== Eprints 3 upgrade ==<br />
I'm keeping a journal of our upgrade/migration from eprints2 to '''eprints3''': [[User:Ckeene/ep3_upgrade]]<br />
<br />
== Stuff I've done related to eprints ==<br />
# I manage http://eprints.sussex.ac.uk for the University of Sussex <br />
# We have some background information http://www.sussex.ac.uk/library/ir/<br />
# and a not very much updated news/blog http://researchonline.lib.sussex.ac.uk/<br />
<br />
# I have made available some very simple analog config files and perl scripts for producing web usage statistics: [[Files/Simple_usage_statistics_(using_analog)]]<br />
<br />
<br />
== misc ==<br />
A Test:<br />
[[User:Ckeene/page2]]</div>Ckeene