MetaToo System Administration Guide Franck Falcoz Christian Tønsberg MetaToo System Administration Guide by Franck Falcoz
Subversion Identifier: $Id: docbook.xml 1048 2008-01-31 08:36:23Z franck $ EditionCopyright 2005 Technical Knowledge Center of Denmark (DTV), Technical University of Denmark (DTU)
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy
of the license is included in the appendix entitled "GNU Free Documentation License".
Revision 1 October 2006 Revised by: chtRelease corresponding to software release 1.6
Table of Contents I. Initial Preparations Disposition: Describing what needs to be done in order to make MetaToo operational as a webapplication for online cataloguing of metadata: Install, Configure (formats, forms, screens, etc), Load (of existing records). Chapter 1. Installation
A MetaToo application consist of the MetaToo core as well as an application specific supplement andcustomisation of the core.
Throughout this document, the core may be refered to as "fit" (for historic reasons) or as "the metatoocore".
The target system for the installation must be UNIX. The software packages are particularly well suitedfor Debian Linux, but should work with other UNIX variants. 1.1. From Source
Installation on a UNIX system involves the following:
1. Acquire the MetaToo core software package (http://toolxite.net/metatoo/) as well as the MetaToo
supplement packages relevant for the application.
2. Make sure that the software upon which MetaToo depends are present on the target system. The
setup script (see below) will provide you with a list of missing packages upon startup. Also, makesure that a database user with appropriate privileges exist. This database user should either haveprivileges to create databases or - in the case an already existing database is to be used - have allprivileges on that existing database.
3. Unpack the core package and the application package in the same directory. The core package will
have be named fit.ver where ver will usually be a 3 digit version number (e.g. fit.1.4.5). Thename of the application directory can be anything. For the purpose of this document, we will refer toit as app/
The rest of the installation takes place from within the app/ directory.
4. Make any necessary adjustments of the configuration file config.in. The various entries are
described in . In most cases, no adjustments are needed.
5. In the app/ directory, run the setup script setup as superuser (root):
This script will start an interactive dialog with the installer and subsequently:
• check the target system for existence of necessary Perl modules,
• perform the necessary database actions to create the necessary table structure,
• install the necessary code on the target system, and
• upload to the database the content of various definitions (formats, forms, etc) located in the source
The setup dialog will ask for the following:
The dialog will start by asking for a service name - vname - for the installation. Default value isthe value for configuration parameter PACKAGE.
Informations regarding the database used for the installation.
The mail address to which MetaToo system mails are sent. Should be the application manageror the system administrator.
The passwords for the two special users associated with any MetaToo installation.
After these informations are fed to the setup script, it will establish the MetaToo database.
Application specific - as well as core - definitions are then loaded into the database.
Finally, various codefiles are copied to their location beneath the cgi-bin directory of the targetsystem. During the copy, the files are renamed, introducing the chosen service name as prefix. 1.1.1. Installing an Additional Version of The Application
An application may be installed more than once on the target system, for example, for test purpose.
Making a second installation of an application is done by making a new installation of the MetaToosupplement packages relevant for the application into directory app2/ which should reside as sibling to
app/, and then repeat step 4 and 5 of the install procedure described above. Make sure to:
• choose a service name at the begining of the dialog which is different from the service name chosen
• choose database parameters for a database different from the one used for the first installation.
As with a first-time installation, it is important that the database user is allowed to create databases (orthat the database is readily created at setup time). Chapter 2. Configuration Chapter 3. Defining XML MetaData
describing formats and introducing forms and their relations
II. Administrative Maintenance
Disposition: Describing how to configure metatoo: format design, formi design, screen design (images,stylesheets, etc), lookups (internal, external). Also, user-maintenance, authorisation, workflow, etc. Intended audience: Application Managers
Chapter 4. Format Design
Choose Administration -> Formats -> New Use xpaths (without prefix /) with one addition:foo/bar/.body allow content to an element which has nothing else than attributes as its children
Chapter 5. Form Setup
Cataloguing form setup is a process which influence both the input experience when actually using theform to catalogue metadata as well as the structure of the resulting xml metadata.
The form design is the process of determining
• which elements the resulting xml metadata should contain; their names and their structure
• for each field, which kind of input widget should be used to input content to fields
• the associated text elements associated with fields when cataloguing: Labels and help
• the associated cataloguing actions which should be available for fields.
The form customisation is the process of determining the apperance of the input form in the cataloguersbrowser.
A form is designed and/or customised by logging in as admin, choose "administration" and choose the"Forms" menu.
If the form in question does not exist, create it either by duplicating an existing or by creatig a new bypressing "New".
Locate the form in question in the list of forms and press "Edit". This will bring up the design andcustomisation form for the form in question.
The following sections will describe the setup possibilities for the form in question by describing thecontent and use of this design and customisation form. 5.1. Design
Disposition: Describe includes, groups, properties, labels, help, actions. 5.2. Customisation
The cataloguing form for - as well as the view of - a metadata record are created by merging an xmlrepresentation of the record data with eXtensible Stylesheet Language (XSL) stylesheets, and theresulting HTML is then rendered by the cataloguers browser using Cascading Style Sheets (CSS).
For a specific form, the choice of XSL stylesheets is done by selecting from the dropdown "XSLStylesheet" near the top.
MetaToo ships with a limited selection of XSL stylesheets, each defining a basic visual structure anddesign for catalouging forms. If a more application specific layout is needed, it is possible to supplementthis list with alternative stylesheet(s).
Each XSL stylesheet has an associated CSS stylesheet. Depending on the degree of customisability in theHTML produced by the XSL, this CSS determines a number of styling parameters for the apperance ofthe cataloguing form in the browser.
A form specific appeaance is obtained by overloading the associated CSS. This is done by redefining(parts of) the CSS in the input field "CSS" near the top.
In the design process of the actual browser experience of a certain form, FireFox eqiped with theWebDeveloper plugin - and perhaps even with the mozdev plugin - is recommended.
Below, the structure of the output of each of the default XSL is briefly described, as well as the mostrelevant CSS classes to change. 5.2.1. XSL: standard_form
This XSL represents a layout of the input form which is historically inspired: The structure of its outputresembles that of the HTML producd by earlier versions of MetaToo.
The descriptive area - the left hand side of the form - is organised in columns with fixed width. Labels forgroups and fields on the top level is set in the first column, labels for groups and fields on the second levelis set in the secenond column, etc. The number of columns are determinded by the depth of the form.
Labelwise, groups are layed out with its label vertically aligned with the label of the first subfield orsubgroup.
Buttons for collapsion/expansion of groups, adding new occerences (repeat), reordering occurences(move up and move down) as well as buttons for longhelp and lookup are located in the vicinity of thelabel; either immedialtely after it or right justified in its column.
Help texts are placed as it is described in the design and customisation form: Either below or to the rightof input boxes, below the label or as the first line of a group.
The class controlling the whole form. Its width should be defined in accordance with the width forthe descriptive area and the width for the input area.
The class controlling the input area - the right hand side of the form, containing the input boxes. Itswidth should be set in accordance width the width of the individual input boxes as well as the totalwidth of any horisontally layed out groups.
The class styling the columns of the descriptive areas. Their width should be chosen acording to thelabeltexts in a form, making the linebreaking visually tolerable. III. Getting Data Into and Out of
Disposition: 1) Describing how to load data into MetaToo 2) Describing how to access cataloguedmetadata. Describing the Data Access Service (DAS)
Chapter 6. Delivering Data Downstream: The Data Access Service (DAS)
Making records and associated digital objects catalogued with MetaToo available outside of MetaToo isdone via communication through the Data Access Service, or DAS.
A client program can use DAS as a web service for retrieving records as well as for registering backinformations for records and their associated digital objects. Note: by default, this service is only accessible from localhost, if you wish to grant external access, add auth.ip to the configuration file with a space separated list of IP addresses: e.g. das.ip 127.0.0.1 192.168.1.2
This chapter describes the communication. 6.1. REST based DAS API for Retrieving Records
The DAS is called for record retrieval as http://yourserver/cgi-bin/yourapp_das?key=val&.&key=val,where the possible keys (and their values) are described below. 6.1.1. Search related
a single record ID or a comma separated list of record IDs. timestamp
either a unix timestamp (seconds since EPOCH) or a timestamp in the formatYYYYMMDDHHMMSS or 1957-03-20T20:30:00.
an abitrary where clause which can be used to select records based, at this time, on the id, udate,cdate, status, grp, uid and type. Chapter 6. Delivering Data Downstream: The Data Access Service (DAS)6.1.2. Format related
if set to ’short’, the record XML is not returned
if equal to 1, the result will be compressed with gzip
if equal to 1, the XML returned will be indented
if equal to 1, the records returned will be extractly like in the database and will not include, amongother things, authority text mapping
6.1.3. Others firstRecord
the number of the first record to be returned, starting from 1 (default: 1).
the authentication key, which must match configuration option das.key, if it is defined
the maximum number of records returned (default: 100000). 6.1.4. Changes done to database records
The following changes are done to the database record when not using the raw argument: Adding of fit namespace to admin fields
All fields and attributes under /<root>/admin are modified to use the fit namespace. Change update timestamps
All Unix timestamps under //admin/cataloguer/timestamp are changed to ISO8601 dates in localtime without timezone. Adding release dates
The first date of cataloguer publication under a new status is added as admin/released, with theattribute status giving the status code and the body being an ISO8601 date as described above. Chapter 6. Delivering Data Downstream: The Data Access Service (DAS)Change of authority attribute to fit namespace
All attributes with the name authority or authority_* are moved to the fit namespace. Modifications done through the export configuration in Metatoo
Metatoo can be configured to modified records upon export. If you have a file ’export.cat_doc.xml’in your application xml directory, changes defined in the file will be applied to your record in DAS. 6.2. Example Response
<das:records xmlns:das="http://toolxite.net/ns/metatoo/das/" hits="37">➊
<das:record id="34" status="O3">
<das:object id="e674fb0fce2b68381cc47dca7ed5782a" type="image/gif"
<das:record id="46" status="O4">
<das:record id="15" status="D"/>
<das:select>select id from cat_doc</das:select>
Chapter 6. Delivering Data Downstream: The Data Access Service (DAS)
In this example the we get back three records from the puller. The maxRecords parameter was set to 3and we can see my comparing //diagnostic/result/total and returned that the reply in incomplete. An errorof type warning also indicates that this is a partial reply. To view the next two records, you would need touse the same request but this time setting firstRecord to 4.
The attribute /records/record/@id is the metatoo internal identifier for that record. The attribute/records/record/@status is the status of the record, in the example above, you can see that the record asstatus D which stands for deleted. Deteted records are returned as a closed tag with just the id and statusattributes. The object field is a pointer to a file uploaded with the record. Using the object/@id attribute itis possible to link the actual file section in you record to the object/@uri. 6.3. REST based DAS API for Retrieving Digital Objects
The DAS is called for Digital Object retrieval as http://yourserver/cgi-bin/yourapp_das/doc/CKSUM,where CKSUM is the MetaToo internl identifier (checksum) for the digital object.
This URL can be constructed from a DAS record retrieval response by combining the url for the DASwith the "uri" attribute of the <das:object> element. 6.4. REST based DAS API for Registering Back Information
A client using the DAS interface to extract records may register back information for records (e.g. id’sfrom various staorage or handler services) as well as for objects associated with records.
The REST based interface for that resides onhttp://yourserver/cgi-bin/yourapp_das/extid?key=val&.&key=val, where the keys are described below.
The type of the external id. Typically an identifier of the recieving system. Chapter 6. Delivering Data Downstream: The Data Access Service (DAS)
The identifier (cksum) of a MetaToo object related to the record. Use this if the registration is forthe digital object rather than for the record itself. 6.5. REST based DAS API for Retrieving Authorities
In order to retrieve an xml representation of authority ’foobar’, the DAS is called for authorities ashttp://yourserver/cgi-bin/yourapp_das?tab=fit_authority&where=name=’foobar’
If an element in a DAS record retrieval response was catalogued by a form in which authority(dropdown) ’quez’ were used for this element, the element will carry an attribute ’fit:auth_quez’. Chapter 7. Authorisation data: The Auth Service
This service is designed to be used by external service to discover some of the Metatoo authorisationdata for a specified user. For example, a search interface could have a direct link to edit a record butunless authorisation information is available, that system has no way of knowing if the user is actuallyallowed to edit the record. Note: by default, this service is only accessible from localhost, if you wish to grant external access, add auth.ip to the configuration file with a space separated list of IP addresses: e.g. auth.ip 127.0.0.1 192.168.1.2
This authorisation service is REST based and takes a single user ID as parameter: e.g. http://localhost/cgi-bin/urbit_auth?id=root
The result is an XML record with the following main elements: diagnostic: internal diagnostic, fields:fields from the authentication record, flags: authorisation flags, groups: main and extra groups this userbelongs to. Example record:
Chapter 7. Authorisation data: The Auth Service
This service does not return table level authorisation information because the resulting XML would betoo complicated and hard to use by an external service anyway.
You can however deduce some things based on your authentication rules. For example, by default a useris always able to edit is own records, this will mean that darcimm user will be able to edit all his ownrecords.
Further more, there are super-user flags defined which allows a user to edit records of a certain time ifthey are part of a group to which he belongs. For example, the user above has the flag document_su_land has access to group dtu_imm, which means he will be able to edit all dtu_imm literature records. Appendix A. GNU Free Documentation License
Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copiesof this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or otherfunctional and useful document "free" in the sense of freedom: toassure everyone the effective freedom to copy and redistribute it,with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a wayto get credit for their work, while not being considered responsiblefor modifications made by others.
This License is a kind of "copyleft", which means that derivativeworks of the document must themselves be free in the same sense. Itcomplements the GNU General Public License, which is a copyleftlicense designed for free software.
We have designed this License in order to use it for manuals for freesoftware, because free software needs free documentation: a freeprogram should come with manuals providing the same freedoms that thesoftware does. But this License is not limited to software manuals;it can be used for any textual work, regardless of subject matter orwhether it is published as a printed book. We recommend this Licenseprincipally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, thatcontains a notice placed by the copyright holder saying it can bedistributed under the terms of this License. Such a notice grants aworld-wide, royalty-free license, unlimited in duration, to use thatwork under the conditions stated herein. The "Document", below,refers to any such manual or work. Any member of the public is alicensee, and is addressed as "you". You accept the license if you
Appendix A. GNU Free Documentation License
copy, modify or distribute the work in a way requiring permissionunder copyright law.
A "Modified Version" of the Document means any work containing theDocument or a portion of it, either copied verbatim, or withmodifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section ofthe Document that deals exclusively with the relationship of thepublishers or authors of the Document to the Document’s overall subject(or to related matters) and contains nothing that could fall directlywithin that overall subject. (Thus, if the Document is in part atextbook of mathematics, a Secondary Section may not explain anymathematics.) The relationship could be a matter of historicalconnection with the subject or with related matters, or of legal,commercial, philosophical, ethical or political position regardingthem.
The "Invariant Sections" are certain Secondary Sections whose titlesare designated, as being those of Invariant Sections, in the noticethat says that the Document is released under this License. If asection does not fit the above definition of Secondary then it is notallowed to be designated as Invariant. The Document may contain zeroInvariant Sections. If the Document does not identify any InvariantSections then there are none.
The "Cover Texts" are certain short passages of text that are listed,as Front-Cover Texts or Back-Cover Texts, in the notice that says thatthe Document is released under this License. A Front-Cover Text maybe at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy,represented in a format whose specification is available to thegeneral public, that is suitable for revising the documentstraightforwardly with generic text editors or (for images composed ofpixels) generic paint programs or (for drawings) some widely availabledrawing editor, and that is suitable for input to text formatters orfor automatic translation to a variety of formats suitable for inputto text formatters. A copy made in an otherwise Transparent fileformat whose markup, or absence of markup, has been arranged to thwartor discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amountof text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plainASCII without markup, Texinfo input format, LaTeX input format, SGMLor XML using a publicly available DTD, and standard-conforming simpleHTML, PostScript or PDF designed for human modification. Examples of
Appendix A. GNU Free Documentation License
transparent image formats include PNG, XCF and JPG. Opaque formatsinclude proprietary formats that can be read and edited only byproprietary word processors, SGML or XML for which the DTD and/orprocessing tools are not generally available, and themachine-generated HTML, PostScript or PDF produced by some wordprocessors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,plus such following pages as are needed to hold, legibly, the materialthis License requires to appear in the title page. For works informats which do not have any title page as such, "Title Page" meansthe text near the most prominent appearance of the work’s title,preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whosetitle either is precisely XYZ or contains XYZ in parentheses followingtext that translates XYZ in another language. (Here XYZ stands for aspecific section name mentioned below, such as "Acknowledgements","Dedications", "Endorsements", or "History".) To "Preserve the Title"of such a section when you modify the Document means that it remains asection "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice whichstates that this License applies to the Document. These WarrantyDisclaimers are considered to be included by reference in thisLicense, but only as regards disclaiming warranties: any otherimplication that these Warranty Disclaimers may have is void and hasno effect on the meaning of this License.
You may copy and distribute the Document in any medium, eithercommercially or noncommercially, provided that this License, thecopyright notices, and the license notice saying this License appliesto the Document are reproduced in all copies, and that you add no otherconditions whatsoever to those of this License. You may not usetechnical measures to obstruct or control the reading or furthercopying of the copies you make or distribute. However, you may acceptcompensation in exchange for copies. If you distribute a large enoughnumber of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, andyou may publicly display copies. Appendix A. GNU Free Documentation License
If you publish printed copies (or copies in media that commonly haveprinted covers) of the Document, numbering more than 100, and theDocument’s license notice requires Cover Texts, you must enclose thecopies in covers that carry, clearly and legibly, all these CoverTexts: Front-Cover Texts on the front cover, and Back-Cover Texts onthe back cover. Both covers must also clearly and legibly identifyyou as the publisher of these copies. The front cover must presentthe full title with all words of the title equally prominent andvisible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preservethe title of the Document and satisfy these conditions, can be treatedas verbatim copying in other respects.
If the required texts for either cover are too voluminous to fitlegibly, you should put the first ones listed (as many as fitreasonably) on the actual cover, and continue the rest onto adjacentpages.
If you publish or distribute Opaque copies of the Document numberingmore than 100, you must either include a machine-readable Transparentcopy along with each Opaque copy, or state in or with each Opaque copya computer-network location from which the general network-usingpublic has access to download using public-standard network protocolsa complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps,when you begin distribution of Opaque copies in quantity, to ensurethat this Transparent copy will remain thus accessible at the statedlocation until at least one year after the last time you distribute anOpaque copy (directly or through your agents or retailers) of thatedition to the public.
It is requested, but not required, that you contact the authors of theDocument well before redistributing any large number of copies, to givethem a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document underthe conditions of sections 2 and 3 above, provided that you releasethe Modified Version under precisely this License, with the ModifiedVersion filling the role of the Document, thus licensing distributionand modification of the Modified Version to whoever possesses a copyof it. In addition, you must do these things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions(which should, if there were any, be listed in the History section
Appendix A. GNU Free Documentation License
of the Document). You may use the same title as a previous versionif the original publisher of that version gives permission.
B. List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the ModifiedVersion, together with at least five of the principal authors of theDocument (all of its principal authors, if it has fewer than five),unless they release you from this requirement.
C. State on the Title page the name of the publisher of the
D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under theterms of this License, in the form shown in the Addendum below.
G. Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document’s license notice.
H. Include an unaltered copy of this License. I. Preserve the section Entitled "History", Preserve its Title, and add
to it an item stating at least the title, year, new authors, andpublisher of the Modified Version as given on the Title Page. Ifthere is no section Entitled "History" in the Document, create onestating the title, year, authors, and publisher of the Document asgiven on its Title Page, then add an item describing the ModifiedVersion as stated in the previous sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewisethe network locations given in the Document for previous versionsit was based on. These may be placed in the "History" section. You may omit a network location for a work that was published atleast four years before the Document itself, or if the originalpublisher of the version it refers to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the section allthe substance and tone of each of the contributor acknowledgementsand/or dedications given therein.
L. Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbersor the equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled "Endorsements"
or to conflict in title with any Invariant Section.
O. Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections orappendices that qualify as Secondary Sections and contain no materialcopied from the Document, you may at your option designate some or all
Appendix A. GNU Free Documentation License
of these sections as invariant. To do this, add their titles to thelist of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it containsnothing but endorsements of your Modified Version by variousparties--for example, statements of peer review or that the text hasbeen approved by an organization as the authoritative definition of astandard.
You may add a passage of up to five words as a Front-Cover Text, and apassage of up to 25 words as a Back-Cover Text, to the end of the listof Cover Texts in the Modified Version. Only one passage ofFront-Cover Text and one of Back-Cover Text may be added by (orthrough arrangements made by) any one entity. If the Document alreadyincludes a cover text for the same cover, previously added by you orby arrangement made by the same entity you are acting on behalf of,you may not add another; but you may replace the old one, on explicitpermission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this Licensegive permission to use their names for publicity for or to assert orimply endorsement of any Modified Version.
You may combine the Document with other documents released under thisLicense, under the terms defined in section 4 above for modifiedversions, provided that you include in the combination all of theInvariant Sections of all of the original documents, unmodified, andlist them all as Invariant Sections of your combined work in itslicense notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, andmultiple identical Invariant Sections may be replaced with a singlecopy. If there are multiple Invariant Sections with the same name butdifferent contents, make the title of each such section unique byadding at the end of it, in parentheses, the name of the originalauthor or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list ofInvariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History"in the various original documents, forming one section Entitled"History"; likewise combine any sections Entitled "Acknowledgements",and any sections Entitled "Dedications". You must delete all sectionsEntitled "Endorsements". Appendix A. GNU Free Documentation License
You may make a collection consisting of the Document and other documentsreleased under this License, and replace the individual copies of thisLicense in the various documents with a single copy that is included inthe collection, provided that you follow the rules of this License forverbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distributeit individually under this License, provided you insert a copy of thisLicense into the extracted document, and follow this License in allother respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separateand independent documents or works, in or on a volume of a storage ordistribution medium, is called an "aggregate" if the copyrightresulting from the compilation is not used to limit the legal rightsof the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does notapply to the other works in the aggregate which are not themselvesderivative works of the Document.
If the Cover Text requirement of section 3 is applicable to thesecopies of the Document, then if the Document is less than one half ofthe entire aggregate, the Document’s Cover Texts may be placed oncovers that bracket the Document within the aggregate, or theelectronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the wholeaggregate.
Translation is considered a kind of modification, so you maydistribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires specialpermission from their copyright holders, but you may includetranslations of some or all Invariant Sections in addition to theoriginal versions of these Invariant Sections. You may include atranslation of this License, and all the license notices in theDocument, and any Warranty Disclaimers, provided that you also includethe original English version of this License and the original versionsof those notices and disclaimers. In case of a disagreement between
Appendix A. GNU Free Documentation License
the translation and the original version of this License or a noticeor disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements","Dedications", or "History", the requirement (section 4) to Preserveits Title (section 1) will typically require changing the actualtitle.
You may not copy, modify, sublicense, or distribute the Document exceptas expressly provided for under this License. Any other attempt tocopy, modify, sublicense or distribute the Document is void, and willautomatically terminate your rights under this License. However,parties who have received copies, or rights, from you under thisLicense will not have their licenses terminated so long as suchparties remain in full compliance.
The Free Software Foundation may publish new, revised versionsof the GNU Free Documentation License from time to time. Such newversions will be similar in spirit to the present version, but maydiffer in detail to address new problems or concerns. Seehttp://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of thisLicense "or any later version" applies to it, you have the option offollowing the terms and conditions either of that specified version orof any later version that has been published (not as a draft) by theFree Software Foundation. If the Document does not specify a versionnumber of this License, you may choose any version ever published (notas a draft) by the Free Software Foundation.
PHENOTYPIC AND GENOTYPIC CHARACTERIZATION OF LACTOBACILLUS SAKEI ISOLATED FROM PORTUGUESE FERMENTED MEAT PRODUCTS FOR TETRACYCLINE RESISTANCE Martins, A., Makita, M., Fernandes M.H., Fernandes M.J., Barreto A.S. and Fraqueza, 1Faculty of Veterinary Medicine, UTLisbon, Centro de Investigação Interdisciplinar em Sanidade Animal (CIISA), Av. da Universidade Técnica, Pólo Univ
EFFIE-GALA 2012 28 Jahre IAA EFFIE Award Einmal Platin, siebenmal Gold, achtmal Silber, dreimal Bronze „Marketerin des Jahres“ Dr. Kristin Hanusch-Linser, ÖBB Holding AG Erfolgreichste Agenturen 2011 Erfolgreichste Agenturen aller Zeiten EFFIE-Gala 2012 28 Jahre EFFI(E)ziente Marktkommunikation Die EFFIE-Gala mit der Vergabe des begehrten Effi