Information Technology Reference
In-Depth Information
of resources. TAGSYS provides the interfaces for
other systems to store their annotation information,
and recommends resources based on the annota-
tions or other information such as the tags from
Wikipedia. For example, a user can annotate the
resource when he visits applications integrated
with TAGSYS services. These systems are loosely
coupled with TAGSYS, and only need to provide
a data structure including system id, user id and
resource id. Then they can get the services of
feedback and recommendation from TAGSYS,
such as finding similar users.
In this section, we introduce the five atomic
clouds supporting an Institutional Repository. In
the next section, we will introduce our tools to help
with the building of an Institutional Repository.
configure the frameset based user interface, and
add new functions as required. The document
of how to add a new function is provided. The
construction of a common web application is
done by using ant script. In the build file, users
can configure the basic information of the ap-
plication such as application name, description,
running port, database user name and password
etc. After the application is created, a simple ant
command can run it.
The most valuable function of Template is
that it supports the creation of an Institutional
Repository based on the DRSC model.
As depicted in figure 7, the process to create
an Institutional Repository includes three com-
ponents: digital resource descriptions, Menu6
framework and a set of template files. The digital
resource descriptions include the metadata, the
functions, and the constraints. The descriptions
are defined in an XML file. Template receives
the descriptions and uses ant to invoke Free-
maker templates to create the related Java files,
JSP files and configuration files such as Struts,
Spring and Hibernate configuration files, which
are in the Menu6 framework. The generated IR
core is built and running on Tomcat. It calls the
services provided by the five clouds. It also has
a Web interface contained in Menu6 framework
and provides the functions of adding, deleting,
updating and querying. If you want to extend the
functions of the basic Institutional Repository,
you can follow our instructions similar to the
first method.
During the process, the key step is to give out
the descriptions of the digital resources. Writing
XML files by hand often brings some unexpected
errors, thus we provide an interface to input the
metadata and other information. For the moment,
we only provide the function to generate the codes
for one kind of digital resource. If there is more
than one kind of digital resource, the codes have
to be generated separately, and merged together
manually. In the future, we will support multiple
kinds of digital resources. And we will provide
6. TOOL AND PROCESS
OF BUILDING AN IR
We provide a tool called Template to help the
creation of an Institutional Repository. It is based
on our SCA framework named MenuFrame, and
the current version is 6.0 (shorthand as Menu6).
This framework consists of the following modules:
role management, user management, central-
authentication, workflow, component library
and user interface. The target of the framework
is to decrease the effort of setting up an applica-
tion. Developers can focus on their own specific
requirements without spending too much time on
routinely tedious work. This framework supplies
the application with two kinds of interfaces: GUI
interface and service interface. The GUI interface
is a frameset based Web pages. The customization
of menus and privileges is provided. The service
interface can be set up easily because Mule ESB
is embedded.
Based on this framework, we provide two
methods to create new applications. The first
method is to create a common Web-based ap-
plication. The application is generated with role,
user, menu and privilege management. Users can
Search WWH ::
Custom Search