Dobrica Pavlinušić's random unstructured stuff
eprints: Revision 14
Contents


Documents with departments and security settings

select
 archive.eprintid,department,security
from archive,document
where document.eprintid = archive.eprintid and department like '%informacijske%';

Update access to staffonly

begin;
update document set security='staffonly' where eprintid in ( select eprintid from archive where department like '%informacijske%' );
commit;

Repository

backup

# prefix all commands with: sudo -u eprints /usr/share/eprints3/bin/
export ffzg archive XMLFiles > /tmp/ffzg.xmlfile
export ffzg subject XML > /tmp/submject.xml
export ffzg user XML > /tmp/user.xml

restore

http://wiki.eprints.org/w/API:bin/import

epadmin erase_data ffzg

import_subjects --verbose --force --xml ffzg /tmp/submject.xml
import --verbose --migration ffzg user XML /tmp/user.xml
import --verbose --migration ffzg eprint XML /tmp/ffzg.xmlfile

generate_static ffzg
generate_views ffzg

importing from other data source

When generating xml file for import documented at http://wiki.eprints.org/w/XML_Export_Format from some other dataset using --update is useful to re-run import

sudo -u eprints /usr/share/eprints3/bin/import --verbose --migration --enable-file-imports --update grf eprint XML xml

File can be specified in <url> tag using file:///path/on/the/disk/file.pdf but you need --unable-file-imports for this to work!

HASH in export filters with multilang fields

Even better solution which should work across updates is described at: http://www.eprints.org/tech.php/16125.html and our local changes are in eprints-SimpleMultilang.zip

REST API

http://www.eprints.org/tech.php/17435.html

There is an experimental REST interface that lives at /rest/. You will
need to give your user the 'rest' role (e.g. in cfg.d/user_roles.pl):

$c->{user_roles}->{admin} = qw{   rest   general   ... };

(reload Apache to apply the change)

This is driven by EPrints/Apache/REST.pm. One mention of it here:
http://wiki.eprints.org/w/New_Features_in_EPrints_3.2#REST

Otherwise, I'm working on support CRUD/REST for EPrints URIs:

http://wiki.eprints.org/w/API:EPrints/Apache/CRUD

CRUD is missing the ability to update records - what is normally "POST" to an existing URI.