Perintah Eprints di Terminal

epadmin createSetelah berhasil menginstal eprints pada pada tuorial sebelumnya, maka yang perlu mas brow ketahui …dibawah ini merupakan perintah-perintah untuk meng eksekusi mbah eprints melalui terminal….

Arguments:
epadmin create
START HERE! This option will walk you through the tasks needed
to create your repository.

epadmin test *repository_id*
A null operation which just checks your configuration files are
OK and that you can connect to the database. If no
*repository_id* is specified loads each repository in turn. Use
–verbose to generate more information.

epadmin cleanup_cachemaps *repository_id*
Drop any orphaned cache tables.

epadmin config_core *repository_id*
Set hostname, contact email and repository name.

epadmin config_db *repository_id*
Set database connection properties and, optionally, to create
database and database user.

epadmin create_db *repository_id*
Create a database and database user with the current settings.

epadmin create_tables *repository_id*
Create the database tables.

epadmin create_user *repository_id*
Create a new user. You need to do this to create your first
admin account.

epadmin schema *repository_id*
Use this to produce a schema for the EP3 XML read/written by
your repository.

epadmin erase_fulltext_index *repository_id*
This erases all the .words and .indexcodes cache files from your
repository, forcing the indexer to rerun the tools used to
extract full text from your documents.

This is useful if you only setup the fulltext indexing after
your repository is already live, or if you discover there has
been a problem.

epadmin rebuild_triples *repository_id* [*dataset_id* [*item_id*
*item_id* …]]
Queue all the records to have their RDF triple cache rebuilt.
This may tie-up the indexer for some time on a large repository.
Do this if you have made changes to the way RDF triples are
produced from an EPrint.

epadmin recommit *repository_id* *dataset_id* [*eprint_id* *eprint_id*
…]
Recommit all the records in the given dataset. What this does is
cause the automatic values to be re-calculated. If a list of
eprint_ids is given then just recommit those.

epadmin reindex *repository_id* *dataset_id* [*eprint_id* *eprint_id*
…]
Schedule the dataset for reindexing. The indexer will do the
actual indexing and it may take some time. This only schedules
the reindexing. If a list of eprint_ids is given then just
reindex those.

epadmin reorder *repository_id* *dataset_id* [*eprint_id* *eprint_id*
…]
Regenerate the order values for the dataset. If a list of
eprint_ids is given then just recalculate ordervalues for those.

epadmin rehash *repository_id* [*document_id*]
Recalculate the hashes of the files in this document and write
it to a probity log file. If a document id is given then just
generate the hash for that document.

epadmin reload *repository_id*
Cause the web server to reload the repository configuration.

epadmin set_developer_mode *repository_id* <on|off>
While set to on developer mode causes the web server to reload
the repository configuration on every page request. This makes
development much quicker but must not be left switched on in a
production environment since it increases server load
dramatically.

epadmin refresh_views *repository_id*
Tell the webserver that all views pages must be regenerated. The
webserver will update them next time they are requested. Also
causes config to be reloaded.

epadmin refresh_abstracts *repository_id*
Tell the webserver that all abstract summary pages must be
regenerated. The webserver will update them next , but won’t
update them again unless something on the EPrint changes or you
re-run refresh abstracts. Also causes config to be reloaded.

epadmin redo_mime_type *repository_id* dataset [ objectid, … ]
Re-run the file format identification. Dataset may be one of
‘document’ or ‘file’. If ‘document’ only re-does the
identification of the main files in documents.

epadmin redo_thumbnails *repository_id* [ *eprintid*, … ]
Regenerate all the thumbnail and image-preview files and any
other things which are triggered if the document file changed.
Optionally supply a list of eprint ids to re-generate thumbnails
for.

epadmin erase_data *repository_id*
Erases and recreates the database. Removes all documents and
files. Does not touch the configuration files.

epadmin erase_eprints *repository_id*
Erases all the documents and eprints (including their files).
Recreates the eprint and document tables. Leaves configuration
files and the users and subjects tables alone.

epadmin unit_tests
Run unit tests, printing the results to STDOUT. If everything
passed will exit with a return code of 0.

epadmin profile *test*
Run a performance profile of *test* using Devel::NYTProf.

epadmin remove_field *repository_id* *dataset* *field_id*
Remove the database entries for the given field, can not be
undone!

epadmin update *repository_id*
This will add tables and columns to your SQL database to bring
it in-line with your current configuration. It will not remove
data. Use with caution on a live database. Database backup is
recommended befire use on live systems.

epadmin upgrade *repository_id*
After upgrading EPrints, use this to update the database tables.
It will advise any other tasks that are required.

epadmin –help

Options:
–help  Print a brief help message and exit.

–man   Print the full manual page and then exit.

–quiet This option does not do anything.

–verbose
Explain in detail what is going on. May be repeated for greater
effect.

–force Be more forceful (don’t ask for confirmation).

–version
Output version information and exit.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: