EPrints Technical Mailing List Archive
Message: #01588
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] repository administration: frontend or backend?
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] repository administration: frontend or backend?
- From: "Pavlovic,Karlo" <karlo.pavlovic@imp.ac.at>
- Date: Tue, 19 Feb 2013 09:25:11 +0000
Dear all, I am trying to costumise our repository and I have a general question (with two examples): Should things be changed using the frontend (i.e., admin>config.tools), if possible, or should generally be used the backend (as generally described in the wiki: http://wiki.eprints.org/w/Category:Howto). E.g., if using the frontend to add an institutional hierarchy, there is the possibility to go to admin>config.tools>editsubjects. But after adding such a new tree (as an administrator), it does not appear when adding an eprint (as an author). Also, adding metadata fields does not work: When going to admin>config.tools>ManageMetadataFields, a click to e.g. "Eprints:View Dataset Fields" results in this: "EPrints System Error: Attempt to get value from not existent field: metafield/objectid" Thank you! Best, Karlo -- Max Perutz Library Dr. Bohr-Gasse 7 A-1030 Wien T ++43 (01) 79730-3690 http://library.imp.ac.at
- Prev by Date: [EP-tech] ISI Citation Data Import Script
- Next by Date: [EP-tech] Re: ISI Citation Data Import Script
- Previous by thread: [EP-tech] ISI Citation Data Import Script
- Next by thread: [EP-tech] Re: repository administration: frontend or backend?
- Index(es):