Repository configuration - Revision history

Af05v@ecs.soton.ac.uk: /* citations-languageid.xml */

2015-02-23T11:58:33Z

citations-languageid.xml

← Older revision		Revision as of 11:58, 23 February 2015
Line 392:		Line 392:

	; <tt> <ep:linkhere> </tt> : This element is replaced with an XHTML anchor linking to the item. If this citation is being rendered without a link then it is just removed (but not the contents).		; <tt> <ep:linkhere> </tt> : This element is replaced with an XHTML anchor linking to the item. If this citation is being rendered without a link then it is just removed (but not the contents).
	; <ep:iflink> : The contents of this element are only preserved if we are rendering this citation as a link. Maybe an icon which you don't want if it's not a link.		; <tt> <ep:iflink> </tt> : The contents of this element are only preserved if we are rendering this citation as a link. Maybe an icon which you don't want if it's not a link.
	; <ep:ifnotlink> : The opposite of iflink.		; <tt> <ep:ifnotlink> </tt> : The opposite of iflink.
	; <ep:ifset ref="fieldname"> : The contents of this element are only preserved if the field "fieldname" has a value.		; <tt> <ep:ifset ref="fieldname"> </tt> : The contents of this element are only preserved if the field "fieldname" has a value.
	; <ep:ifnotset ref="fieldname"> : The contents of this element are only preserved if the field "fieldname" does not have a value.		; <tt> <ep:ifnotset ref="fieldname"> </tt> : The contents of this element are only preserved if the field "fieldname" does not have a value.
	; <ep:ifmatch name="fieldname(s)" value="searchparam"> : This is the swiss army knife of the world of conditional rendering. It is also a bit complicated, and few people will need to use it. This actually works like a single search element. The attributes are:		; <tt> <ep:ifmatch name="fieldname(s)" value="searchparam"> </tt> : This is the swiss army knife of the world of conditional rendering. It is also a bit complicated, and few people will need to use it. This actually works like a single search element. The attributes are:
	;; name : This is the name of one or more fields, specified as in the search fields configuration. eg. "title/abstract"		;; name : This is the name of one or more fields, specified as in the search fields configuration. eg. "title/abstract"
	;; value : This is a value to search for. Treated like the value entered in a search field.		;; value : This is a value to search for. Treated like the value entered in a search field.
Line 409:		Line 409:

	This will render (approx) after years before 1950. Neat eh?		This will render (approx) after years before 1950. Neat eh?
	; <ep:ifnotmatch name="fieldname(s)" value="searchparam"> : Like ifmatch but only includes the values inside if the search does not match.		; <tt><ep:ifnotmatch name="fieldname(s)" value="searchparam"> </tt> : Like ifmatch but only includes the values inside if the search does not match.

	==metadata-types.xml==		==metadata-types.xml==

Th.lauke@arcor.de: misspelling corrected

2010-12-22T09:44:40Z

misspelling corrected

← Older revision		Revision as of 09:44, 22 December 2010
Line 56:		Line 56:

	===Language specific files.===		===Language specific files.===
	phrases, ~~template~~ and citations have one instance per supported language. This allows the system to generate pages and emails in more than one language. Supporting a new language will require translating ~~the~~ all ~~the english in~~ the english config files currently shipped. If you do intend it do this (lots of work!) please get in touch with the eprints admin so that we can avoid duplicated effort.		phrases, templates and citations have one instance per supported language. This allows the system to generate pages and emails in more than one language. Supporting a new language will require translating all the english config files currently shipped. If you do intend to do this (lots of work!) please get in touch with the eprints admin so that we can avoid duplicated effort.

	===Extra Entities===		===Extra Entities===

Pm705 at 12:42, 20 March 2010

2010-03-20T12:42:22Z

← Older revision		Revision as of 12:42, 20 March 2010
Line 1:		Line 1:
	{{development}}		{{development}}
	{{manual}}		{{manual}}
	[[Category:~~Configuration~~]]		[[Category:Howto]]
	==EPrints Archive Configuration==		==EPrints Archive Configuration==
	This section describes all the configuration files in an single archive in the EPrints system.		This section describes all the configuration files in an single archive in the EPrints system.

Pm705 at 16:51, 8 February 2010

2010-02-08T16:51:11Z

← Older revision		Revision as of 16:51, 8 February 2010
Line 1:		Line 1:
	{{development}}		{{development}}
	{{manual}}		{{manual}}
			[[Category:Configuration]]
	==EPrints Archive Configuration==		==EPrints Archive Configuration==
	This section describes all the configuration files in an single archive in the EPrints system.		This section describes all the configuration files in an single archive in the EPrints system.

Fmccown: /* XHTML */ Some cleanup

2007-03-02T18:56:27Z

XHTML: Some cleanup

← Older revision		Revision as of 18:56, 2 March 2007
Line 32:		Line 32:

	===XHTML===		===XHTML===
	~~This~~ files use HTML elements (and other elements too). XHTML is a fairly new version of HTML which is ~~back~~ compatable with HTML 4 but written using XML not SGML. This means that it is much stricter but less ambiguous and easier to parse and modify. Assuming you know HTML, the main differences are as follows:		These files use HTML elements (and other elements too). XHTML is a fairly new version of HTML which is backwards compatable with HTML 4 but written using XML, not SGML. This means that it is much stricter but less ambiguous and easier to parse and modify. Assuming you know HTML, the main differences are as follows:

	; ~~Tags~~ must be closed : All elements must be closed, even ones such as <li>. Tags which do not have a close tag in HTML, like <tt> <br> </tt> or <tt> <img src="foo"> </tt> still must be closed eg. <tt> <img src="foo"></img> </tt> - this can be abbreviated ~~to the neater looking~~: <tt> <img src="foo" /> </tt>		; All tags must be closed : All elements must be closed, even ones such as <li>. Tags which do not have a close tag in HTML, like <tt><br></tt> or <tt><img src="foo"></tt> still must be closed eg. <tt><img src="foo"></img></tt> - this can be abbreviated as: <tt> <img src="foo" /></tt>
	; All tags and attributes must be lower case : Self explanitary.		; All tags and attributes must be lower case : Self explanitary.
	; Strict definition of what tags may appear within ~~which~~ others. : Not actually checked by EPrints. It will let any rubbish past as long as it's valid XML. But that's no reason to be naughty.		; Strict definition of what tags may appear within others : Not actually checked by EPrints. It will let any rubbish past as long as it's valid XML. But that's no reason to be naughty.
	; All attributes must be wrapped in quotes : In HTML the values of attributes do not have to be wrapped in quotes, but in XML (and therefore XHTML) they do.		; All attributes must be wrapped in quotes : In HTML the values of attributes do not have to be wrapped in quotes, but in XML (and therefore XHTML) they do.
	; All attributes must have a value : In HTML some attribues ~~did~~ not require a value, for example in <tt> <hr noshade> </tt> ~~elements.~~ In XHTML it is represented as <tt> <hr noshade="noshade" /> </tt>		; All attributes must have a value : In HTML some attribues do not require a value, for example <tt><hr noshade></tt> In XHTML it is represented as <tt> <hr noshade="noshade" /> </tt>

	So in summary, the HTML:		So in summary, the HTML:


	<code>		<code>
	<img SRC=someurl>		<img SRC=someurl>
Line 49:		Line 47:
	</code>		</code>
	should become in XHTML:		should become in XHTML:


	<code>		<code>
	<img src="someurl" />		<img src="someurl" />

Moj at 12:21, 3 January 2007

2007-01-03T12:21:24Z

← Older revision		Revision as of 12:21, 3 January 2007
Line 1:		Line 1:
			{{development}}
	{{manual}}		{{manual}}
	==EPrints Archive Configuration==		==EPrints Archive Configuration==

Kiz: /* ruler.xml */

2006-06-26T15:10:51Z

ruler.xml

← Older revision		Revision as of 15:10, 26 June 2006
Line 469:		Line 469:
	This file configures the horizontal divider which eprints uses, which is inserted in place of &ruler;		This file configures the horizontal divider which eprints uses, which is inserted in place of &ruler;

	If you have no great dislike of <lt>hr<gt> horizontal rulers then you can leave it alone.		If you have no great dislike of <hr /> horizontal rulers then you can leave it alone.

	You can't use entities like &frontpage; in ruler.		You can't use entities like &frontpage; in ruler.

Kiz: /* Name Spaces and XHTML */

2006-06-26T15:09:20Z

Name Spaces and XHTML

← Older revision		Revision as of 15:09, 26 June 2006
Line 83:		Line 83:

	<code>		<code>
	<ep:phrase ref="lib/session:contact"><p>Feel free to contact		<ep:phrase ref="lib/session:contact"><p>Feel free to contact
	<a href="mailto:&adminemail;">&archivename; administration</a>		<a href="mailto:&adminemail;">&archivename; administration</a>
	with details.</p></ep:phrase>		with details.</p></ep:phrase>

	eprints elements: phrase		eprints elements: phrase
	xhtml elements: p, a		xhtml elements: p, a
	eprints entities: archiveemail, archivename		eprints entities: archiveemail, archivename
	</code>		</code>

	==The Primary Archive Configuration File==		==The Primary Archive Configuration File==
	This XML file appears in the <tt>archives/</tt> directory, usually <tt>/opt/eprints2/archives/</tt>, it describes the most very basic details about the archive. It is generated (and modified) by configure_archive and will not normally need to be edited.		This XML file appears in the <tt>archives/</tt> directory, usually <tt>/opt/eprints2/archives/</tt>, it describes the most very basic details about the archive. It is generated (and modified) by configure_archive and will not normally need to be edited.

Kiz: /* Extra Entities */

2006-06-26T15:06:33Z

Extra Entities

← Older revision		Revision as of 15:06, 26 June 2006
Line 61:		Line 61:

	===Extra Entities===		===Extra Entities===
	The XML files all use a DTD which defines a few extra entities. Entities are items in XML (or HTML) which start with "&" and end with ";" like &. These additional entities come from the entities DTD file created by generate_entities. One DTD is created per language, although currently the only variation is the archive name.		The XML files all use a DTD which defines a few extra entities. Entities are items in XML (or HTML) which start with "&" and end with ";" like &amp;. These additional entities come from the entities DTD file created by generate_entities. One DTD is created per language, although currently the only variation is the archive name.

	; &archivename; : The name of the archive in the current language.		; &archivename; : The name of the archive in the current language.
Line 71:		Line 71:
	; &version; : The current EPrints version.		; &version; : The current EPrints version.
	; &ruler; : The XHTML of the standard divider.		; &ruler; : The XHTML of the standard divider.
	; Any XHTML character entity (since EPrints v2.1) : You may now use any XHTML character entity, eg. <tt>  é €</tt>.		; Any XHTML character entity (since EPrints v2.1) : You may now use any XHTML character entity, eg. <tt>&nbsp; &eacute; &euro;</tt>.
	; User configured entities : You can generate your own entities by modifying the function which generates them in ArchiveConfig.pm		; User configured entities : You can generate your own entities by modifying the function which generates them in ArchiveConfig.pm

Kiz: /* XHTML */

2006-06-26T15:04:58Z

XHTML

← Older revision		Revision as of 15:04, 26 June 2006
Line 37:		Line 37:
	; Strict definition of what tags may appear within which others. : Not actually checked by EPrints. It will let any rubbish past as long as it's valid XML. But that's no reason to be naughty.		; Strict definition of what tags may appear within which others. : Not actually checked by EPrints. It will let any rubbish past as long as it's valid XML. But that's no reason to be naughty.
	; All attributes must be wrapped in quotes : In HTML the values of attributes do not have to be wrapped in quotes, but in XML (and therefore XHTML) they do.		; All attributes must be wrapped in quotes : In HTML the values of attributes do not have to be wrapped in quotes, but in XML (and therefore XHTML) they do.
	; All attributes must have a value : In HTML some attribues did not require a value, for example in <tt> <hr noshade> </tt> elements. In XHTML it is represented as <tt> <hr noshade="noshade" /> </tt>		; All attributes must have a value : In HTML some attribues did not require a value, for example in <tt> <hr noshade> </tt> elements. In XHTML it is represented as <tt> <hr noshade="noshade" /> </tt>

	So in summary, the HTML:		So in summary, the HTML:
Line 43:		Line 43:

	<code>		<code>
	<img SRC=someurl>		<img SRC=someurl>
	<hr NOSHADE WIDTH=2>		<hr NOSHADE WIDTH=2>
	<P>Foo bar</P>		<P>Foo bar</P>
	</code>		</code>
	should become in XHTML:		should become in XHTML:
Line 51:		Line 51:

	<code>		<code>
	<img src="someurl" />		<img src="someurl" />
	<hr noshade="noshade" width="2" />		<hr noshade="noshade" width="2" />
	<p>Foo bar</p>		<p>Foo bar</p>
	</code>		</code>
	And that's more or less it. See http://www.w3c.org/ for a complete description.		And that's more or less it. See http://www.w3c.org/ for a complete description.