Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F63276000
index.html.wml
No One
Temporary
Actions
Download File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Subscribers
None
File Metadata
Details
File Info
Storage
Attached
Created
Sat, May 18, 23:51
Size
10 KB
Mime Type
text/x-c
Expires
Mon, May 20, 23:51 (2 d)
Engine
blob
Format
Raw Data
Handle
17754067
Attached To
R3600 invenio-infoscience
index.html.wml
View Options
## $Id$
## This file is part of the CERN Document Server Software (CDSware).
## Copyright (C) 2002, 2003, 2004, 2005 CERN.
##
## The CDSware is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## The CDSware is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDSware; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
#include "cdspage.wml" \
title="<MSG_ADMIN_AREA>" \
navbar_name="admin" \
navtrail_previous_links="" \
navbar_select="admin"
Welcome to the Admin Area of the <CDSNAME>. You'll find here pointers
to the available runtime admin-level interfaces and admin-level guides
on how to configure and run the CDSware system.
<p>CDSware comes as a suite of several more or less independent
modules. You'll find brief descriptions for each admin module below.
(More background information on each module may be read in the <a
href="<WEBURL>/hacking/modules.html">modules overview</a> article.)
<h3>Admin HOWTO guides</h3>
<p><a href="howto/">Admin HOWTO Guides</a> give you you both short and
not-so-short recipes and thoughts on some of the most frequently
encountered administrative tasks. They tend to answer various
admin-level questions of a rather general level. The specific tasks
are better addressed by module-specific guides and interfaces
presented below.
<h3>Data acquisition related modules</h3>
<p>The metadata input into a running CDSware system can be done in two
ways: <em>(i) admin-oriented batch mode</em>,
i.e. <strong>BibHarvest</strong> to get data from OAI repositories,
<strong>BibConvert</strong> to convert any input data into XML MARC,
and <strong>BibUpload</strong> to upload XML MARC files into CDSware;
and <em>(ii) author-oriented interactive mode</em>,
i.e. <strong>WebSubmit</strong> to submit documents via Web. Once the
data are uploaded in CDSware, you may want to modify them via
<strong>BibEdit</strong> to edit the metadata.
<table border="1" cellpadding="2">
<tr>
<th class="searchboxheader">Admin Module</th>
<th class="searchboxheader">Admin Description</th>
<th class="searchboxheader">Admin Interface</th>
<th class="searchboxheader">Admin Guide</th>
</tr>
<tr>
<td>
<strong>BibHarvest Admin</strong>
</td>
<td>
Enables you to configure OAI metadata harvestor for eventual periodical
batch upload of data. For example, you can define from where to
harvest, with what periodicity, how to transform data before
uploading them into CDSware, etc.
</td>
<td>
<a href="bibharvest/bibharvestadmin.py">BibHarvest Admin Interface</a>
</td>
<td>
<a href="bibharvest/guide.html">BibHarvest Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>BibConvert Admin</strong>
</td>
<td>
Explains how to use bibliographic data convertor. Useful for batch
upload of data. For example, when migrating the metadata from
your old system, or when integrating metadata acquisitions from
non-OAI sources, or just about any line-based
not-so-well-structured metadata.
</td>
<td>
<small class=note>command-line program</small>
</td>
<td>
<a href="bibconvert/guide.html">BibConvert Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>BibUpload Admin</strong>
</td>
<td>
Enables you to configure eventual local special operations to be
done on the data being uploaded.
</td>
<td>
<small class=note>command-line program</small>
</td>
<td>
<a href="bibupload/guide.html">BibUpload Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>WebSubmit Admin</strong>
</td>
<td>
Enables you to configure the submit interface and logic for various document types.
For example, you can define which metadata fields should be submitted for various
doctypes, what to do with the inputted values before uploading,
possible peer review and approval strategy, etc.
</td>
<td>
<a href="websubmit/">WebSubmit Admin Interface</a>
</td>
<td>
<a href="websubmit/guide/">WebSubmit Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>BibEdit Admin</strong>
</td>
<td>
Enables you to directly manipulate bibliographic data, edit a single
record, do global replacements, and other cataloguing tasks.
</td>
<td>
<a href="bibedit/bibeditadmin.py">BibEdit Admin Interface</a>
</td>
<td>
<a href="bibedit/guide.html">BibEdit Admin Guide</a>
</td>
</tr>
</table>
<h3>Data provision related modules</h3>
<p>The metadata output from a running CDSware system to the end-user
is covered by several modules: <strong>BibIndex</strong> to index the
metadata, <strong>BibRank</strong> to eventually rank them,
<strong>BibFormat</strong> to format them for the output,
<strong>WebSearch</strong> to provide search interfaces and search
engine.
<table border="1">
<tr>
<th class="searchboxheader">Admin Module</th>
<th class="searchboxheader">Admin Description</th>
<th class="searchboxheader">Admin Interface</th>
<th class="searchboxheader">Admin Guide</th>
</tr>
<tr>
<td>
<strong>BibIndex Admin</strong>
</td>
<td>
Enables you to configure "word files", i.e. to define which
bibliographic fields are indexed into which word indexes. The word
indexes are then used by the search interface. For example, you can
define that the logical author index is constructed from physical
<code>100 $a</code> and <code>700 $a</code> bibliographic tags, you
can force reindexing of the fulltext index, etc.
</td>
<td>
<a href="bibindex/">BibIndex Admin Interface</a>
</td>
<td>
<a href="bibindex/guide.html">BibIndex Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>BibRank Admin</strong>
</td>
<td>
Enables you to configure various ranking methods to be used by the search engine.
You can rebalance existing ranking sets, create new ranking methods, etc.
</td>
<td>
<a href="bibrank/">BibRank Admin Interface</a>
</td>
<td>
<a href="bibrank/guide.html">BibRank Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>BibFormat Admin</strong>
</td>
<td>
Enables you to specify how the bibliographic data is presented to
the end user in the search interface. You can decide that titles should be
presented in bold font, that for each author an automatic link to
author's home page should be created according to some receipt, etc.
</td>
<td>
<a href="bibformat/">BibFormat Admin Interface</a>
</td>
<td>
<a href="bibformat/guide.html">BibFormat Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>WebSearch Admin</strong>
</td>
<td>
Enables you to configure the search interface for various metadata
collections. You can define new collections and organize them in
the tree, you can define various portalboxes that would appear on
the screen, you can define search options and search fields to
present, etc.
</td>
<td>
<a href="websearch/">WebSearch Admin Interface</a>
</td>
<td>
<a href="websearch/guide.html">WebSearch Admin Guide</a>
</td>
</tr>
</table>
<h3>Personalization related modules</h3>
<p>The CDSware interface can be personalized to suit different needs
of different end-users. This functionality is covered by several
modules: <strong>WebSession</strong> to identify users and their
personal configurations, <strong>WebBasket</strong> to provide
personal baskets or document carts, and <strong>WebAlert</strong> to
set up personal email notification alerts.
<table border="1">
<tr>
<th class="searchboxheader">Admin Module</th>
<th class="searchboxheader">Admin Description</th>
<th class="searchboxheader">Admin Interface</th>
<th class="searchboxheader">Admin Guide</th>
</tr>
<tr>
<td>
<strong>WebSession Admin</strong>
</td>
<td>
Enables you to inspect the status of guest sessions and to expire
them; the status and details on registered users, etc.
</td>
<td>
<small class=note>not available, but see the guide for the command-line way</small>
</td>
<td>
<a href="websession/guide.html">WebSession Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>WebBasket Admin</strong>
</td>
<td>
Enables you to inspect and manipulate user baskets set up on the
system, to make them public/private, etc.
</td>
<td>
<small class=note>not available, but see the guide for the command-line way</small>
</td>
<td>
<a href="webbasket/guide.html">WebBasket Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>WebAlert Admin</strong>
</td>
<td>
Enables you to inspect and manipulate user alerts set up on the
system, to run the alert engine, etc.
</td>
<td>
<small class=note>not available, but see the guide for the command-line way</small>
</td>
<td>
<a href="webalert/guide.html">WebAlert Admin Guide</a>
</td>
</tr>
</table>
<h3>System glue modules</h3>
<p>Modules that provide the necessary glue for those presented above
are: <strong>BibSched</strong> to manage and schedule bibliographic
tasks, <strong>WebAccess</strong> to define role-based access control
system to all CDSware services, and <strong>WebStyle</strong> to
define a common look and feel of CDSware web pages.
<table border="1">
<tr>
<th class="searchboxheader">Admin Module</th>
<th class="searchboxheader">Admin Description</th>
<th class="searchboxheader">Admin Interface</th>
<th class="searchboxheader">Admin Guide</th>
</tr>
<tr>
<td>
<strong>BibSched Admin</strong>
</td>
<td>
Enables you to inspect bibliographic task queue, to postpone or
reschedule jobs, to make priorities, to run periodical tasks, etc.
</td>
<td>
<small class=note>command-line program</small>
</td>
<td>
<a href="bibsched/guide.html">BibSched Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>WebAccess Admin</strong>
</td>
<td>
Enables you to define who has got access or admin rights on various CDSware modules.
For example, you can define that John is the bibliographic
data manager, that Jim can modify the search interface pages, that
Jill is the submission approval editor, etc.
</td>
<td>
<a href="webaccess/">WebAccess Admin Interface</a>
</td>
<td>
<a href="webaccess/guide.html">WebAccess Admin Guide</a>
</td>
</tr>
<tr>
<td>
<strong>WebStyle Admin</strong>
</td>
<td>
Enables you to customize default CDSware page style and the CSS style sheet.
</td>
<td>
<small class=note>not available, but see the guide for the command-line way</small>
</td>
<td>
<a href="webstyle/guide.html">WebStyle Admin Guide</a>
</td>
</tr>
</table>
Event Timeline
Log In to Comment