-
Notifications
You must be signed in to change notification settings - Fork 1.3k
/
xmlui.xconf
136 lines (120 loc) · 6.51 KB
/
xmlui.xconf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
<?xml version="1.0"?>
<!DOCTYPE xmlui SYSTEM "xmlui.dtd">
<!--
- xmlui.xconf
-
- Copyright (c) 2002-2009, The DSpace Foundation. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions are
- met:
-
- - Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-
- - Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-
- Neither the name of the DSpace Foundation nor the names of its
- contributors may be used to endorse or promote products derived from
- this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
- ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
- TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
- USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGE.
-->
<!--
- The XMLUI (Manakin Release) configuration file
-
- Authors: Scott Phillips
- Version: $Revision$
- Date: $Date$
-->
<xmlui>
<!--
This section configures the Aspect "chain". An Aspect provides a set
of coupled features for the system. All Aspects are chained together
such that together they form the complete DSpace website. This is where
the chain is defined, the order in which each aspect is declared
determines it's order in the chain. Aspects at the top are invoked
first.
The <aspect> element has two attributes, name & path. The name is used
to identify the Aspect, while the path determines the directory. The
path attribute should be listed exactly as it is found in the
/xmlui/cocoon/aspects/ directory followed by a slash.
-->
<aspects>
<!--
@deprecated: the Artifact Browser has been devided into ViewArtifacts,
BrowseArtifacts, SearchArtifacts
<aspect name="Artifact Browser" path="resource://aspects/ArtifactBrowser/" />
-->
<aspect name="Displaying Artifacts" path="resource://aspects/ViewArtifacts/" />
<aspect name="Browsing Artifacts" path="resource://aspects/BrowseArtifacts/" />
<aspect name="Searching Artifacts" path="resource://aspects/SearchArtifacts/" />
<aspect name="Administration" path="resource://aspects/Administrative/" />
<aspect name="E-Person" path="resource://aspects/EPerson/" />
<aspect name="Submission and Workflow" path="resource://aspects/Submission/" />
<aspect name="Statistics" path="resource://aspects/Statistics/" />
<aspect name="Original Workflow" path="resource://aspects/Workflow/" />
<!--<aspect name="XMLWorkflow" path="resource://aspects/XMLWorkflow/" />-->
<!--
To enable Discovery, uncomment this Aspect that will enable it
within your existing XMLUI
Also make sure to comment the SearchArtifacts aspect
as leaving it on together with discovery will cause UI overlap issues
<aspect name="Discovery" path="resource://aspects/Discovery/" />
-->
<!--<aspect name="SwordClient" path="resource://aspects/SwordClient/" />-->
<!--
This aspect tests the various possible DRI features,
it helps a theme developer create themes
-->
<!-- <aspect name="XML Tests" path="resource://aspects/XMLTest/"/> -->
</aspects>
<!--
This section configures which Theme should apply to a particular URL.
Themes stylize an abstract DRI document (generated by the Aspect
chain from above) and produce XHTML (or possibly another format) for
display to the user. Each theme rule is processed in the order that it
is listed below, the first rule that matches is the theme that is applied.
The <theme> element has several attributes including: name, id, regex,
handle, and path. The name attribute is used to identify the theme, while
the path determines the directory. The path attribute should be listed
exactly as it is found in the /xmlui/cocoon/themes/ directory. Both the
regex and handle attributes determine if the theme rule matches the URL.
If either the pattern or handle attribute is left off then the only the
other component is used to determine matching.
Keep in mind that the order of <theme> elements matters in the case of
overlapping matching rules. For example, a theme rule with a very broad
matching rule (like regex=".*") will override a more specific theme
declaration (like handle="1234/23") if placed before it.
Finally, theme application also "cascades" down to pages derived from the
one that the theme directly applies to. Thus, a theme applied to a
specific community will also apply to that community's collections and
their respective items.
-->
<themes>
<!-- Example configuration -->
<!-- <theme name="Test Theme 1" handle="123456789/1" path="theme1/"/> -->
<!-- <theme name="Test Theme 2" regex="community-list" path="theme2/"/> -->
<!-- Default theme -->
<theme name="Default Reference Theme" regex=".*" path="Reference/" />
<!-- Mirage theme, @mire contribution of new theme to support easier development and branding -->
<!-- <theme name="Atmire Mirage Theme" regex=".*" path="Mirage/" /> -->
<!-- Classic theme, inspired by the JSP UI -->
<!-- <theme name="Classic" regex=".*" path="Classic/" /> -->
<!-- Table based browse display -->
<!-- <theme name="Table Theme" regex=".*" path="TableTheme/" /> -->
</themes>
</xmlui>