Sandbox, a web-based text editor created by the OLIS, is being expanded an re-written to provide enhanced functionality. The new version of Sandbox will become the interface fro access to the UNIX environment for campuses housed on the shared servers when Aleph v.18 becomes available. This change in access to the Aleph servers is due to concerns regarding security.
The SUNYLA Library Software Users Group (LiSUG) submitted questions to the OLIS on the functionality of the new version of Sandbox. Listed below are the questions from LiSUG and the responses provided by the OLIS.
List of Items Needed by Campuses
for New Sandbox/Aleph 18 Access
I. Access to run all Ex Libris Aleph utilities
a.including stop and start all aleph servers, batch
queues, web server, indexing daemons, etc.
b.One utility of great importance is used to test PLIFs
and other aleph sequential files.
•OLIS: Not all utils are used. The necessary ones will
be available in Sandbox and others only in the Aleph Staff
GUI. Many of the utils available in the GUI have the
advantage of providing log files that help with
troubleshooting. The OLIS will provide a list of available
utils and how to access them either through the GUI or in
II. Access to modify and change *all* configuration tables.
a.Includes all aleph library $data_tabs, z-server tables,
web files, www_server.conf, pc_server.conf, icon directory.
b.Ability to add new indexes, modify OCLC match/merge rules,
•OLIS: All campus files will minimally have read access.
Aleph files that have been reserved for Systems personnel
from OLIS and ITEC will have read access.
Configuration files impacting only the WebOPAC will be read
only unless the campus library director provides
authorization to edit. Some other files based on standards
applied across all campuses will be read only. All other
configuration files will have write permissions. The OLIS
will provide a list of files that have read but not write
•OLIS: v18 will be delivered with a suite of available
indexes that includes what the campus had in v16 along
with all other indexes that have been created for all
campuses on the shared servers. Index codes will be
standardized. Requests for new indexes beyond what
would already be available will be reviewed with the
OLIS. Campuses will be asked to submit requests
through Footprints for modifications to OCLC match/merge
rules. These changes will have the advantage of
supporting cooperative data projects such as new book
lists and periodical printout documents and will
significantly aid troubleshooting.
III.Ability to create named backup files
•OLIS: Currently, Sandbox has the capability to copy
html files with the campus three character code. The
functionality will be available in the revised Sandbox
for those campuses that receive permission from their
library director to edit WebOPAC related files.
•OLIS: Please clarify if you are asking about other
functionality. Examples would be helpful.
a.Date stamp in the filename so more than a single
backup is possible.
•OLIS: This feature is in the current Sandbox and will
be carried over into the new Sandbox.
b.Revert function to any previous version of file
•OLIS: The new version of Sandbox will allow for all
versions of the file to be viewable (those files
updated directly on the server and those files updated
through Sandbox). The ability to revert to any version
will be possible.
IV.Ability to view all log files
a.$data_scratch, $alephe_scratch, $LOGDIR,etc.
•OLIS: These files will be available for viewing.
V.Ability to export or load any oracle table
a.To export $data_files using the aleph services
b.To load any table using the aleph services
(p_file_06) or (p_file_04)
•OLIS: All Aleph services will continue to be available
through the GUI.
VI.Ability to download any output file
a.$data_scratch, $alephe_scratch, $data_files, etc.
•OLIS: Options will be supported to provide
functionality to upload and download files to these
directories from third party sources.
•OLIS: Sandbox will also enable files to be moved/copied
across these directories for download through the GUI Task
VII.Access to PL/SQL to produce reports and update
Aleph-related oracle tables.
•OLIS: Oracle report accounts will continue to be
available and can be used with standard ODBC clients.
•OLIS: SQL based Oracle table updates (outside of
capabilities through Aleph Services) will continue to be
done through Footprints requests. These types of
requests could also benefit other campuses and could be
VIII.Ability to create and run shell scripts together
with SQL that might be accessed via the web or the
•OLIS: This functionality will be available as needed.
Requests would be made through Footprints with
information on the script so that it can be added to
Sandbox for the specific campus to run.
IX.Access to $alephe_root/apache/htdocs to place web files
such as new book lists so they can be accessed by web
•OLIS: The v16 to v18 upgrade process will delete all
files currently in the v16 htdocs directory and replace
with new files for v18. One of these files will be a
favicon.ico file. Campuses will have the ability to add a
favicon file and add other files to htdocs directory but
will be asked not to change any other files already there.
Also, campuses would be responsible for maintaining any of
the files they add to htdocs as campus additions may be
impacted by service pack upgrades.
X.Access and ability to customize or add to all xml forms
•OLIS: This functionality currently exists through the
current Sandbox and will continue in the revised version.
XI.Access to code in $alephe_proc and other locations for
aleph and custom reports.
•OLIS: The $alephe_proc is part of the Aleph a-tree which
will not be viewable in Sandbox due to performance and
resource considerations. Given that so few campuses have
staff that work with SQL and custom reports, campuses will
be asked to submit a Footprints request indicating the
files and SQL code they are interested in viewing.
Information will then be made available.
XII.Ability to upload files for services such as EDI, PLIF,
Marcive and Currency
a.Issues with http file transfers for very large files
b.FTP can be automated which cuts down on work (and
remembering to load currency, etc. periodically)
•OLIS: Capabilities for large file transfers will be
available (also see comment on VI). Capability for
automating the ftp of loads (PLIF, currency, etc.) can be
setup for campuses as requested.