diff --git a/drupal/islandora/LICENSE.txt b/drupal/islandora/LICENSE.txt deleted file mode 100644 index 94a9ed024..000000000 --- a/drupal/islandora/LICENSE.txt +++ /dev/null @@ -1,674 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 3, 29 June 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU General Public License is a free, copyleft license for -software and other kinds of works. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -the GNU General Public License is intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. We, the Free Software Foundation, use the -GNU General Public License for most of our software; it applies also to -any other work released this way by its authors. You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - To protect your rights, we need to prevent others from denying you -these rights or asking you to surrender the rights. Therefore, you have -certain responsibilities if you distribute copies of the software, or if -you modify it: responsibilities to respect the freedom of others. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must pass on to the recipients the same -freedoms that you received. You must make sure that they, too, receive -or can get the source code. And you must show them these terms so they -know their rights. - - Developers that use the GNU GPL protect your rights with two steps: -(1) assert copyright on the software, and (2) offer you this License -giving you legal permission to copy, distribute and/or modify it. - - For the developers' and authors' protection, the GPL clearly explains -that there is no warranty for this free software. For both users' and -authors' sake, the GPL requires that modified versions be marked as -changed, so that their problems will not be attributed erroneously to -authors of previous versions. - - Some devices are designed to deny users access to install or run -modified versions of the software inside them, although the manufacturer -can do so. This is fundamentally incompatible with the aim of -protecting users' freedom to change the software. The systematic -pattern of such abuse occurs in the area of products for individuals to -use, which is precisely where it is most unacceptable. Therefore, we -have designed this version of the GPL to prohibit the practice for those -products. If such problems arise substantially in other domains, we -stand ready to extend this provision to those domains in future versions -of the GPL, as needed to protect the freedom of users. - - Finally, every program is threatened constantly by software patents. -States should not allow patents to restrict development and use of -software on general-purpose computers, but in those that do, we wish to -avoid the special danger that patents applied to a free program could -make it effectively proprietary. To prevent this, the GPL assures that -patents cannot be used to render the program non-free. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Use with the GNU Affero General Public License. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU Affero General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the special requirements of the GNU Affero General Public License, -section 13, concerning interaction through a network will apply to the -combination as such. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program. If not, see . - -Also add information on how to contact you by electronic and paper mail. - - If the program does terminal interaction, make it output a short -notice like this when it starts in an interactive mode: - - Copyright (C) - This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, your program's commands -might be different; for a GUI interface, you would use an "about box". - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU GPL, see -. - - The GNU General Public License does not permit incorporating your program -into proprietary programs. If your program is a subroutine library, you -may consider it more useful to permit linking proprietary applications with -the library. If this is what you want to do, use the GNU Lesser General -Public License instead of this License. But first, please read -. diff --git a/drupal/islandora/README.md b/drupal/islandora/README.md deleted file mode 100644 index 9fded0256..000000000 --- a/drupal/islandora/README.md +++ /dev/null @@ -1,21 +0,0 @@ -# Islandora [![Build Status](https://travis-ci.org/Islandora-Labs/islandora.png?branch=7.x-2.x)](https://travis-ci.org/Islandora-Labs/islandora) - -## Introduction - -Islandora Fedora 4 Repository Module - -## Maintainers/Sponsors - -Current maintainers: - -* [Nick Ruest](https://github.com/ruebot) -* [Daniel Lamb](https://github.com/daniel-dgi/) - -## Development - -If you would like to contribute to this module, please check out our helpful [Documentation for Developers](https://github.com/Islandora/islandora/wiki#wiki-documentation-for-developers) info, as well as our [Developers](http://islandora.ca/developers) section on the Islandora.ca site. - -## License - -[GPLv3](http://www.gnu.org/licenses/gpl-3.0.txt) - diff --git a/drupal/islandora/build.xml b/drupal/islandora/build.xml deleted file mode 100644 index fe12c57ce..000000000 --- a/drupal/islandora/build.xml +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/drupal/islandora/build/Doxyfile b/drupal/islandora/build/Doxyfile deleted file mode 100644 index f41dc2858..000000000 --- a/drupal/islandora/build/Doxyfile +++ /dev/null @@ -1,1627 +0,0 @@ -# Doxyfile 1.7.1 - -# This file describes the settings to be used by the documentation system -# doxygen (www.doxygen.org) for a project -# -# All text after a hash (#) is considered a comment and will be ignored -# The format is: -# TAG = value [value, ...] -# For lists items can also be appended using: -# TAG += value [value, ...] -# Values that contain spaces should be placed between quotes (" ") - -#--------------------------------------------------------------------------- -# Project related configuration options -#--------------------------------------------------------------------------- - -# This tag specifies the encoding used for all characters in the config file -# that follow. The default is UTF-8 which is also the encoding used for all -# text before the first occurrence of this tag. Doxygen uses libiconv (or the -# iconv built into libc) for the transcoding. See -# http://www.gnu.org/software/libiconv for the list of possible encodings. - -DOXYFILE_ENCODING = UTF-8 - -# The PROJECT_NAME tag is a single word (or a sequence of words surrounded -# by quotes) that should identify the project. - -PROJECT_NAME = Islandora 7.x - -# Put the git hash here using sed before generating the documentation. -PROJECT_NUMBER = - -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) -# base path where the generated documentation will be put. -# If a relative path is entered, it will be relative to the location -# where doxygen was started. If left blank the current directory will be used. - -OUTPUT_DIRECTORY = build/api - -# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create -# 4096 sub-directories (in 2 levels) under the output directory of each output -# format and will distribute the generated files over these directories. -# Enabling this option can be useful when feeding doxygen a huge amount of -# source files, where putting all generated files in the same directory would -# otherwise cause performance problems for the file system. - -CREATE_SUBDIRS = NO - -# The OUTPUT_LANGUAGE tag is used to specify the language in which all -# documentation generated by doxygen is written. Doxygen will use this -# information to generate all constant output in the proper language. -# The default language is English, other supported languages are: -# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, -# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, -# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English -# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, -# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, -# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. - -OUTPUT_LANGUAGE = English - -# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will -# include brief member descriptions after the members that are listed in -# the file and class documentation (similar to JavaDoc). -# Set to NO to disable this. - -BRIEF_MEMBER_DESC = YES - -# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend -# the brief description of a member or function before the detailed description. -# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the -# brief descriptions will be completely suppressed. - -REPEAT_BRIEF = YES - -# This tag implements a quasi-intelligent brief description abbreviator -# that is used to form the text in various listings. Each string -# in this list, if found as the leading text of the brief description, will be -# stripped from the text and the result after processing the whole list, is -# used as the annotated text. Otherwise, the brief description is used as-is. -# If left blank, the following values are used ("$name" is automatically -# replaced with the name of the entity): "The $name class" "The $name widget" -# "The $name file" "is" "provides" "specifies" "contains" -# "represents" "a" "an" "the" - -ABBREVIATE_BRIEF = - -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then -# Doxygen will generate a detailed section even if there is only a brief -# description. - -ALWAYS_DETAILED_SEC = NO - -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all -# inherited members of a class in the documentation of that class as if those -# members were ordinary class members. Constructors, destructors and assignment -# operators of the base classes will not be shown. - -INLINE_INHERITED_MEMB = NO - -# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full -# path before files name in the file list and in the header files. If set -# to NO the shortest path that makes the file name unique will be used. - -FULL_PATH_NAMES = YES - -# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag -# can be used to strip a user-defined part of the path. Stripping is -# only done if one of the specified strings matches the left-hand part of -# the path. The tag can be used to show relative paths in the file list. -# If left blank the directory from which doxygen is run is used as the -# path to strip. - -STRIP_FROM_PATH = - -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of -# the path mentioned in the documentation of a class, which tells -# the reader which header file to include in order to use a class. -# If left blank only the name of the header file containing the class -# definition is used. Otherwise one should specify the include paths that -# are normally passed to the compiler using the -I flag. - -STRIP_FROM_INC_PATH = - -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter -# (but less readable) file names. This can be useful is your file systems -# doesn't support long names like on DOS, Mac, or CD-ROM. - -SHORT_NAMES = NO - -# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen -# will interpret the first line (until the first dot) of a JavaDoc-style -# comment as the brief description. If set to NO, the JavaDoc -# comments will behave just like regular Qt-style comments -# (thus requiring an explicit @brief command for a brief description.) - -JAVADOC_AUTOBRIEF = YES - -# If the QT_AUTOBRIEF tag is set to YES then Doxygen will -# interpret the first line (until the first dot) of a Qt-style -# comment as the brief description. If set to NO, the comments -# will behave just like regular Qt-style comments (thus requiring -# an explicit \brief command for a brief description.) - -QT_AUTOBRIEF = NO - -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen -# treat a multi-line C++ special comment block (i.e. a block of //! or /// -# comments) as a brief description. This used to be the default behaviour. -# The new default is to treat a multi-line C++ comment block as a detailed -# description. Set this tag to YES if you prefer the old behaviour instead. - -MULTILINE_CPP_IS_BRIEF = NO - -# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented -# member inherits the documentation from any documented member that it -# re-implements. - -INHERIT_DOCS = YES - -# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce -# a new page for each member. If set to NO, the documentation of a member will -# be part of the file/class/namespace that contains it. - -SEPARATE_MEMBER_PAGES = NO - -# The TAB_SIZE tag can be used to set the number of spaces in a tab. -# Doxygen uses this value to replace tabs by spaces in code fragments. - -TAB_SIZE = 8 - -# This tag can be used to specify a number of aliases that acts -# as commands in the documentation. An alias has the form "name=value". -# For example adding "sideeffect=\par Side Effects:\n" will allow you to -# put the command \sideeffect (or @sideeffect) in the documentation, which -# will result in a user-defined paragraph with heading "Side Effects:". -# You can put \n's in the value part of an alias to insert newlines. - -ALIASES = - -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C -# sources only. Doxygen will then generate output that is more tailored for C. -# For instance, some of the names that are used will be different. The list -# of all members will be omitted, etc. - -OPTIMIZE_OUTPUT_FOR_C = NO - -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java -# sources only. Doxygen will then generate output that is more tailored for -# Java. For instance, namespaces will be presented as packages, qualified -# scopes will look different, etc. - -OPTIMIZE_OUTPUT_JAVA = NO - -# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran -# sources only. Doxygen will then generate output that is more tailored for -# Fortran. - -OPTIMIZE_FOR_FORTRAN = NO - -# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL -# sources. Doxygen will then generate output that is tailored for -# VHDL. - -OPTIMIZE_OUTPUT_VHDL = NO - -# Doxygen selects the parser to use depending on the extension of the files it -# parses. With this tag you can assign which parser to use for a given extension. -# Doxygen has a built-in mapping, but you can override or extend it using this -# tag. The format is ext=language, where ext is a file extension, and language -# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, -# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make -# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C -# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions -# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. - -EXTENSION_MAPPING = module=php - -# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want -# to include (a tag file for) the STL sources as input, then you should -# set this tag to YES in order to let doxygen match functions declarations and -# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. -# func(std::string) {}). This also make the inheritance and collaboration -# diagrams that involve STL classes more complete and accurate. - -BUILTIN_STL_SUPPORT = NO - -# If you use Microsoft's C++/CLI language, you should set this option to YES to -# enable parsing support. - -CPP_CLI_SUPPORT = NO - -# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. -# Doxygen will parse them like normal C++ but will assume all classes use public -# instead of private inheritance when no explicit protection keyword is present. - -SIP_SUPPORT = NO - -# For Microsoft's IDL there are propget and propput attributes to indicate getter -# and setter methods for a property. Setting this option to YES (the default) -# will make doxygen to replace the get and set methods by a property in the -# documentation. This will only work if the methods are indeed getting or -# setting a simple type. If this is not the case, or you want to show the -# methods anyway, you should set this option to NO. - -IDL_PROPERTY_SUPPORT = YES - -# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC -# tag is set to YES, then doxygen will reuse the documentation of the first -# member in the group (if any) for the other members of the group. By default -# all members of a group must be documented explicitly. - -DISTRIBUTE_GROUP_DOC = NO - -# Set the SUBGROUPING tag to YES (the default) to allow class member groups of -# the same type (for instance a group of public functions) to be put as a -# subgroup of that type (e.g. under the Public Functions section). Set it to -# NO to prevent subgrouping. Alternatively, this can be done per class using -# the \nosubgrouping command. - -SUBGROUPING = YES - -# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum -# is documented as struct, union, or enum with the name of the typedef. So -# typedef struct TypeS {} TypeT, will appear in the documentation as a struct -# with name TypeT. When disabled the typedef will appear as a member of a file, -# namespace, or class. And the struct will be named TypeS. This can typically -# be useful for C code in case the coding convention dictates that all compound -# types are typedef'ed and only the typedef is referenced, never the tag name. - -TYPEDEF_HIDES_STRUCT = NO - -# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to -# determine which symbols to keep in memory and which to flush to disk. -# When the cache is full, less often used symbols will be written to disk. -# For small to medium size projects (<1000 input files) the default value is -# probably good enough. For larger projects a too small cache size can cause -# doxygen to be busy swapping symbols to and from disk most of the time -# causing a significant performance penality. -# If the system has enough physical memory increasing the cache will improve the -# performance by keeping more symbols in memory. Note that the value works on -# a logarithmic scale so increasing the size by one will rougly double the -# memory usage. The cache size is given by this formula: -# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, -# corresponding to a cache size of 2^16 = 65536 symbols - -SYMBOL_CACHE_SIZE = 0 - -#--------------------------------------------------------------------------- -# Build related configuration options -#--------------------------------------------------------------------------- - -# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in -# documentation are documented, even if no documentation was available. -# Private class members and static file members will be hidden unless -# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES - -EXTRACT_ALL = NO - -# If the EXTRACT_PRIVATE tag is set to YES all private members of a class -# will be included in the documentation. - -EXTRACT_PRIVATE = NO - -# If the EXTRACT_STATIC tag is set to YES all static members of a file -# will be included in the documentation. - -EXTRACT_STATIC = YES - -# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) -# defined locally in source files will be included in the documentation. -# If set to NO only classes defined in header files are included. - -EXTRACT_LOCAL_CLASSES = YES - -# This flag is only useful for Objective-C code. When set to YES local -# methods, which are defined in the implementation section but not in -# the interface are included in the documentation. -# If set to NO (the default) only methods in the interface are included. - -EXTRACT_LOCAL_METHODS = NO - -# If this flag is set to YES, the members of anonymous namespaces will be -# extracted and appear in the documentation as a namespace called -# 'anonymous_namespace{file}', where file will be replaced with the base -# name of the file that contains the anonymous namespace. By default -# anonymous namespace are hidden. - -EXTRACT_ANON_NSPACES = NO - -# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all -# undocumented members of documented classes, files or namespaces. -# If set to NO (the default) these members will be included in the -# various overviews, but no documentation section is generated. -# This option has no effect if EXTRACT_ALL is enabled. - -HIDE_UNDOC_MEMBERS = NO - -# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all -# undocumented classes that are normally visible in the class hierarchy. -# If set to NO (the default) these classes will be included in the various -# overviews. This option has no effect if EXTRACT_ALL is enabled. - -HIDE_UNDOC_CLASSES = NO - -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all -# friend (class|struct|union) declarations. -# If set to NO (the default) these declarations will be included in the -# documentation. - -HIDE_FRIEND_COMPOUNDS = NO - -# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any -# documentation blocks found inside the body of a function. -# If set to NO (the default) these blocks will be appended to the -# function's detailed documentation block. - -HIDE_IN_BODY_DOCS = NO - -# The INTERNAL_DOCS tag determines if documentation -# that is typed after a \internal command is included. If the tag is set -# to NO (the default) then the documentation will be excluded. -# Set it to YES to include the internal documentation. - -INTERNAL_DOCS = NO - -# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate -# file names in lower-case letters. If set to YES upper-case letters are also -# allowed. This is useful if you have classes or files whose names only differ -# in case and if your file system supports case sensitive file names. Windows -# and Mac users are advised to set this option to NO. - -CASE_SENSE_NAMES = YES - -# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen -# will show members with their full class and namespace scopes in the -# documentation. If set to YES the scope will be hidden. - -HIDE_SCOPE_NAMES = NO - -# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen -# will put a list of the files that are included by a file in the documentation -# of that file. - -SHOW_INCLUDE_FILES = YES - -# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen -# will list include files with double quotes in the documentation -# rather than with sharp brackets. - -FORCE_LOCAL_INCLUDES = NO - -# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] -# is inserted in the documentation for inline members. - -INLINE_INFO = YES - -# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen -# will sort the (detailed) documentation of file and class members -# alphabetically by member name. If set to NO the members will appear in -# declaration order. - -SORT_MEMBER_DOCS = YES - -# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the -# brief documentation of file, namespace and class members alphabetically -# by member name. If set to NO (the default) the members will appear in -# declaration order. - -SORT_BRIEF_DOCS = NO - -# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen -# will sort the (brief and detailed) documentation of class members so that -# constructors and destructors are listed first. If set to NO (the default) -# the constructors will appear in the respective orders defined by -# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. -# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO -# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. - -SORT_MEMBERS_CTORS_1ST = NO - -# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the -# hierarchy of group names into alphabetical order. If set to NO (the default) -# the group names will appear in their defined order. - -SORT_GROUP_NAMES = NO - -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be -# sorted by fully-qualified names, including namespaces. If set to -# NO (the default), the class list will be sorted only by class name, -# not including the namespace part. -# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. -# Note: This option applies only to the class list, not to the -# alphabetical list. - -SORT_BY_SCOPE_NAME = NO - -# The GENERATE_TODOLIST tag can be used to enable (YES) or -# disable (NO) the todo list. This list is created by putting \todo -# commands in the documentation. - -GENERATE_TODOLIST = YES - -# The GENERATE_TESTLIST tag can be used to enable (YES) or -# disable (NO) the test list. This list is created by putting \test -# commands in the documentation. - -GENERATE_TESTLIST = YES - -# The GENERATE_BUGLIST tag can be used to enable (YES) or -# disable (NO) the bug list. This list is created by putting \bug -# commands in the documentation. - -GENERATE_BUGLIST = YES - -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or -# disable (NO) the deprecated list. This list is created by putting -# \deprecated commands in the documentation. - -GENERATE_DEPRECATEDLIST= YES - -# The ENABLED_SECTIONS tag can be used to enable conditional -# documentation sections, marked by \if sectionname ... \endif. - -ENABLED_SECTIONS = - -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines -# the initial value of a variable or define consists of for it to appear in -# the documentation. If the initializer consists of more lines than specified -# here it will be hidden. Use a value of 0 to hide initializers completely. -# The appearance of the initializer of individual variables and defines in the -# documentation can be controlled using \showinitializer or \hideinitializer -# command in the documentation regardless of this setting. - -MAX_INITIALIZER_LINES = 30 - -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated -# at the bottom of the documentation of classes and structs. If set to YES the -# list will mention the files that were used to generate the documentation. - -SHOW_USED_FILES = YES - -# If the sources in your project are distributed over multiple directories -# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy -# in the documentation. The default is NO. - -SHOW_DIRECTORIES = NO - -# Set the SHOW_FILES tag to NO to disable the generation of the Files page. -# This will remove the Files entry from the Quick Index and from the -# Folder Tree View (if specified). The default is YES. - -SHOW_FILES = YES - -# Set the SHOW_NAMESPACES tag to NO to disable the generation of the -# Namespaces page. -# This will remove the Namespaces entry from the Quick Index -# and from the Folder Tree View (if specified). The default is YES. - -SHOW_NAMESPACES = YES - -# The FILE_VERSION_FILTER tag can be used to specify a program or script that -# doxygen should invoke to get the current version for each file (typically from -# the version control system). Doxygen will invoke the program by executing (via -# popen()) the command , where is the value of -# the FILE_VERSION_FILTER tag, and is the name of an input file -# provided by doxygen. Whatever the program writes to standard output -# is used as the file version. See the manual for examples. - -FILE_VERSION_FILTER = - -# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed -# by doxygen. The layout file controls the global structure of the generated -# output files in an output format independent way. The create the layout file -# that represents doxygen's defaults, run doxygen with the -l option. -# You can optionally specify a file name after the option, if omitted -# DoxygenLayout.xml will be used as the name of the layout file. - -LAYOUT_FILE = - -#--------------------------------------------------------------------------- -# configuration options related to warning and progress messages -#--------------------------------------------------------------------------- - -# The QUIET tag can be used to turn on/off the messages that are generated -# by doxygen. Possible values are YES and NO. If left blank NO is used. - -QUIET = NO - -# The WARNINGS tag can be used to turn on/off the warning messages that are -# generated by doxygen. Possible values are YES and NO. If left blank -# NO is used. - -WARNINGS = YES - -# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings -# for undocumented members. If EXTRACT_ALL is set to YES then this flag will -# automatically be disabled. - -WARN_IF_UNDOCUMENTED = YES - -# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for -# potential errors in the documentation, such as not documenting some -# parameters in a documented function, or documenting parameters that -# don't exist or using markup commands wrongly. - -WARN_IF_DOC_ERROR = YES - -# This WARN_NO_PARAMDOC option can be abled to get warnings for -# functions that are documented, but have no documentation for their parameters -# or return value. If set to NO (the default) doxygen will only warn about -# wrong or incomplete parameter documentation, but not about the absence of -# documentation. - -WARN_NO_PARAMDOC = NO - -# The WARN_FORMAT tag determines the format of the warning messages that -# doxygen can produce. The string should contain the $file, $line, and $text -# tags, which will be replaced by the file and line number from which the -# warning originated and the warning text. Optionally the format may contain -# $version, which will be replaced by the version of the file (if it could -# be obtained via FILE_VERSION_FILTER) - -WARN_FORMAT = "$file:$line: $text" - -# The WARN_LOGFILE tag can be used to specify a file to which warning -# and error messages should be written. If left blank the output is written -# to stderr. - -WARN_LOGFILE = - -#--------------------------------------------------------------------------- -# configuration options related to the input files -#--------------------------------------------------------------------------- - -# The INPUT tag can be used to specify the files and/or directories that contain -# documented source files. You may enter file names like "myfile.cpp" or -# directories like "/usr/src/myproject". Separate the files or directories -# with spaces. - -INPUT = - -# This tag can be used to specify the character encoding of the source files -# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is -# also the default input encoding. Doxygen uses libiconv (or the iconv built -# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for -# the list of possible encodings. - -INPUT_ENCODING = UTF-8 - -# If the value of the INPUT tag contains directories, you can use the -# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp -# and *.h) to filter out the source-files in the directories. If left -# blank the following patterns are tested: -# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx -# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 - -FILE_PATTERNS = *.module *.inc *.php - -# The RECURSIVE tag can be used to turn specify whether or not subdirectories -# should be searched for input files as well. Possible values are YES and NO. -# If left blank NO is used. - -RECURSIVE = YES - -# The EXCLUDE tag can be used to specify files and/or directories that should -# excluded from the INPUT source files. This way you can easily exclude a -# subdirectory from a directory tree whose root is specified with the INPUT tag. - -EXCLUDE = tests build - -# The EXCLUDE_SYMLINKS tag can be used select whether or not files or -# directories that are symbolic links (a Unix filesystem feature) are excluded -# from the input. - -EXCLUDE_SYMLINKS = NO - -# If the value of the INPUT tag contains directories, you can use the -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude -# certain files from those directories. Note that the wildcards are matched -# against the file with absolute path, so to exclude all test directories -# for example use the pattern */test/* - -EXCLUDE_PATTERNS = - -# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names -# (namespaces, classes, functions, etc.) that should be excluded from the -# output. The symbol name can be a fully qualified name, a word, or if the -# wildcard * is used, a substring. Examples: ANamespace, AClass, -# AClass::ANamespace, ANamespace::*Test - -EXCLUDE_SYMBOLS = - -# The EXAMPLE_PATH tag can be used to specify one or more files or -# directories that contain example code fragments that are included (see -# the \include command). - -EXAMPLE_PATH = - -# If the value of the EXAMPLE_PATH tag contains directories, you can use the -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp -# and *.h) to filter out the source-files in the directories. If left -# blank all files are included. - -EXAMPLE_PATTERNS = - -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be -# searched for input files to be used with the \include or \dontinclude -# commands irrespective of the value of the RECURSIVE tag. -# Possible values are YES and NO. If left blank NO is used. - -EXAMPLE_RECURSIVE = NO - -# The IMAGE_PATH tag can be used to specify one or more files or -# directories that contain image that are included in the documentation (see -# the \image command). - -IMAGE_PATH = - -# The INPUT_FILTER tag can be used to specify a program that doxygen should -# invoke to filter for each input file. Doxygen will invoke the filter program -# by executing (via popen()) the command , where -# is the value of the INPUT_FILTER tag, and is the name of an -# input file. Doxygen will then use the output that the filter program writes -# to standard output. -# If FILTER_PATTERNS is specified, this tag will be -# ignored. - -INPUT_FILTER = - -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern -# basis. -# Doxygen will compare the file name with each pattern and apply the -# filter if there is a match. -# The filters are a list of the form: -# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further -# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER -# is applied to all files. - -FILTER_PATTERNS = - -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using -# INPUT_FILTER) will be used to filter the input files when producing source -# files to browse (i.e. when SOURCE_BROWSER is set to YES). - -FILTER_SOURCE_FILES = NO - -#--------------------------------------------------------------------------- -# configuration options related to source browsing -#--------------------------------------------------------------------------- - -# If the SOURCE_BROWSER tag is set to YES then a list of source files will -# be generated. Documented entities will be cross-referenced with these sources. -# Note: To get rid of all source code in the generated output, make sure also -# VERBATIM_HEADERS is set to NO. - -SOURCE_BROWSER = NO - -# Setting the INLINE_SOURCES tag to YES will include the body -# of functions and classes directly in the documentation. - -INLINE_SOURCES = NO - -# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct -# doxygen to hide any special comment blocks from generated source code -# fragments. Normal C and C++ comments will always remain visible. - -STRIP_CODE_COMMENTS = YES - -# If the REFERENCED_BY_RELATION tag is set to YES -# then for each documented function all documented -# functions referencing it will be listed. - -REFERENCED_BY_RELATION = NO - -# If the REFERENCES_RELATION tag is set to YES -# then for each documented function all documented entities -# called/used by that function will be listed. - -REFERENCES_RELATION = NO - -# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) -# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from -# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will -# link to the source code. -# Otherwise they will link to the documentation. - -REFERENCES_LINK_SOURCE = YES - -# If the USE_HTAGS tag is set to YES then the references to source code -# will point to the HTML generated by the htags(1) tool instead of doxygen -# built-in source browser. The htags tool is part of GNU's global source -# tagging system (see http://www.gnu.org/software/global/global.html). You -# will need version 4.8.6 or higher. - -USE_HTAGS = NO - -# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen -# will generate a verbatim copy of the header file for each class for -# which an include is specified. Set to NO to disable this. - -VERBATIM_HEADERS = YES - -#--------------------------------------------------------------------------- -# configuration options related to the alphabetical class index -#--------------------------------------------------------------------------- - -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index -# of all compounds will be generated. Enable this if the project -# contains a lot of classes, structs, unions or interfaces. - -ALPHABETICAL_INDEX = YES - -# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then -# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns -# in which this list will be split (can be a number in the range [1..20]) - -COLS_IN_ALPHA_INDEX = 5 - -# In case all classes in a project start with a common prefix, all -# classes will be put under the same header in the alphabetical index. -# The IGNORE_PREFIX tag can be used to specify one or more prefixes that -# should be ignored while generating the index headers. - -IGNORE_PREFIX = - -#--------------------------------------------------------------------------- -# configuration options related to the HTML output -#--------------------------------------------------------------------------- - -# If the GENERATE_HTML tag is set to YES (the default) Doxygen will -# generate HTML output. - -GENERATE_HTML = YES - -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `html' will be used as the default path. - -HTML_OUTPUT = html - -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for -# each generated HTML page (for example: .htm,.php,.asp). If it is left blank -# doxygen will generate files with .html extension. - -HTML_FILE_EXTENSION = .html - -# The HTML_HEADER tag can be used to specify a personal HTML header for -# each generated HTML page. If it is left blank doxygen will generate a -# standard header. - -HTML_HEADER = - -# The HTML_FOOTER tag can be used to specify a personal HTML footer for -# each generated HTML page. If it is left blank doxygen will generate a -# standard footer. - -HTML_FOOTER = - -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading -# style sheet that is used by each HTML page. It can be used to -# fine-tune the look of the HTML output. If the tag is left blank doxygen -# will generate a default style sheet. Note that doxygen will try to copy -# the style sheet file to the HTML output directory, so don't put your own -# stylesheet in the HTML output directory as well, or it will be erased! - -HTML_STYLESHEET = - -# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. -# Doxygen will adjust the colors in the stylesheet and background images -# according to this color. Hue is specified as an angle on a colorwheel, -# see http://en.wikipedia.org/wiki/Hue for more information. -# For instance the value 0 represents red, 60 is yellow, 120 is green, -# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. -# The allowed range is 0 to 359. - -HTML_COLORSTYLE_HUE = 220 - -# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of -# the colors in the HTML output. For a value of 0 the output will use -# grayscales only. A value of 255 will produce the most vivid colors. - -HTML_COLORSTYLE_SAT = 100 - -# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to -# the luminance component of the colors in the HTML output. Values below -# 100 gradually make the output lighter, whereas values above 100 make -# the output darker. The value divided by 100 is the actual gamma applied, -# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, -# and 100 does not change the gamma. - -HTML_COLORSTYLE_GAMMA = 80 - -# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML -# page will contain the date and time when the page was generated. Setting -# this to NO can help when comparing the output of multiple runs. - -HTML_TIMESTAMP = YES - -# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, -# files or namespaces will be aligned in HTML using tables. If set to -# NO a bullet list will be used. - -HTML_ALIGN_MEMBERS = YES - -# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML -# documentation will contain sections that can be hidden and shown after the -# page has loaded. For this to work a browser that supports -# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox -# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). - -HTML_DYNAMIC_SECTIONS = NO - -# If the GENERATE_DOCSET tag is set to YES, additional index files -# will be generated that can be used as input for Apple's Xcode 3 -# integrated development environment, introduced with OSX 10.5 (Leopard). -# To create a documentation set, doxygen will generate a Makefile in the -# HTML output directory. Running make will produce the docset in that -# directory and running "make install" will install the docset in -# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find -# it at startup. -# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html -# for more information. - -GENERATE_DOCSET = NO - -# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the -# feed. A documentation feed provides an umbrella under which multiple -# documentation sets from a single provider (such as a company or product suite) -# can be grouped. - -DOCSET_FEEDNAME = "Doxygen generated docs" - -# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that -# should uniquely identify the documentation set bundle. This should be a -# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen -# will append .docset to the name. - -DOCSET_BUNDLE_ID = org.doxygen.Project - -# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify -# the documentation publisher. This should be a reverse domain-name style -# string, e.g. com.mycompany.MyDocSet.documentation. - -DOCSET_PUBLISHER_ID = org.doxygen.Publisher - -# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. - -DOCSET_PUBLISHER_NAME = Publisher - -# If the GENERATE_HTMLHELP tag is set to YES, additional index files -# will be generated that can be used as input for tools like the -# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) -# of the generated HTML documentation. - -GENERATE_HTMLHELP = NO - -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can -# be used to specify the file name of the resulting .chm file. You -# can add a path in front of the file if the result should not be -# written to the html output directory. - -CHM_FILE = - -# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can -# be used to specify the location (absolute path including file name) of -# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run -# the HTML help compiler on the generated index.hhp. - -HHC_LOCATION = - -# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag -# controls if a separate .chi index file is generated (YES) or that -# it should be included in the master .chm file (NO). - -GENERATE_CHI = NO - -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING -# is used to encode HtmlHelp index (hhk), content (hhc) and project file -# content. - -CHM_INDEX_ENCODING = - -# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag -# controls whether a binary table of contents is generated (YES) or a -# normal table of contents (NO) in the .chm file. - -BINARY_TOC = NO - -# The TOC_EXPAND flag can be set to YES to add extra items for group members -# to the contents of the HTML help documentation and to the tree view. - -TOC_EXPAND = NO - -# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and -# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated -# that can be used as input for Qt's qhelpgenerator to generate a -# Qt Compressed Help (.qch) of the generated HTML documentation. - -GENERATE_QHP = NO - -# If the QHG_LOCATION tag is specified, the QCH_FILE tag can -# be used to specify the file name of the resulting .qch file. -# The path specified is relative to the HTML output folder. - -QCH_FILE = - -# The QHP_NAMESPACE tag specifies the namespace to use when generating -# Qt Help Project output. For more information please see -# http://doc.trolltech.com/qthelpproject.html#namespace - -QHP_NAMESPACE = org.doxygen.Project - -# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating -# Qt Help Project output. For more information please see -# http://doc.trolltech.com/qthelpproject.html#virtual-folders - -QHP_VIRTUAL_FOLDER = doc - -# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to -# add. For more information please see -# http://doc.trolltech.com/qthelpproject.html#custom-filters - -QHP_CUST_FILTER_NAME = - -# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the -# custom filter to add. For more information please see -# -# Qt Help Project / Custom Filters. - -QHP_CUST_FILTER_ATTRS = - -# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this -# project's -# filter section matches. -# -# Qt Help Project / Filter Attributes. - -QHP_SECT_FILTER_ATTRS = - -# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can -# be used to specify the location of Qt's qhelpgenerator. -# If non-empty doxygen will try to run qhelpgenerator on the generated -# .qhp file. - -QHG_LOCATION = - -# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files -# will be generated, which together with the HTML files, form an Eclipse help -# plugin. To install this plugin and make it available under the help contents -# menu in Eclipse, the contents of the directory containing the HTML and XML -# files needs to be copied into the plugins directory of eclipse. The name of -# the directory within the plugins directory should be the same as -# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before -# the help appears. - -GENERATE_ECLIPSEHELP = NO - -# A unique identifier for the eclipse help plugin. When installing the plugin -# the directory name containing the HTML and XML files should also have -# this name. - -ECLIPSE_DOC_ID = org.doxygen.Project - -# The DISABLE_INDEX tag can be used to turn on/off the condensed index at -# top of each HTML page. The value NO (the default) enables the index and -# the value YES disables it. - -DISABLE_INDEX = NO - -# This tag can be used to set the number of enum values (range [1..20]) -# that doxygen will group on one line in the generated HTML documentation. - -ENUM_VALUES_PER_LINE = 4 - -# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index -# structure should be generated to display hierarchical information. -# If the tag value is set to YES, a side panel will be generated -# containing a tree-like index structure (just like the one that -# is generated for HTML Help). For this to work a browser that supports -# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). -# Windows users are probably better off using the HTML help feature. - -GENERATE_TREEVIEW = NO - -# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, -# and Class Hierarchy pages using a tree view instead of an ordered list. - -USE_INLINE_TREES = NO - -# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be -# used to set the initial width (in pixels) of the frame in which the tree -# is shown. - -TREEVIEW_WIDTH = 250 - -# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open -# links to external symbols imported via tag files in a separate window. - -EXT_LINKS_IN_WINDOW = NO - -# Use this tag to change the font size of Latex formulas included -# as images in the HTML documentation. The default is 10. Note that -# when you change the font size after a successful doxygen run you need -# to manually remove any form_*.png images from the HTML output directory -# to force them to be regenerated. - -FORMULA_FONTSIZE = 10 - -# Use the FORMULA_TRANPARENT tag to determine whether or not the images -# generated for formulas are transparent PNGs. Transparent PNGs are -# not supported properly for IE 6.0, but are supported on all modern browsers. -# Note that when changing this option you need to delete any form_*.png files -# in the HTML output before the changes have effect. - -FORMULA_TRANSPARENT = YES - -# When the SEARCHENGINE tag is enabled doxygen will generate a search box -# for the HTML output. The underlying search engine uses javascript -# and DHTML and should work on any modern browser. Note that when using -# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets -# (GENERATE_DOCSET) there is already a search function so this one should -# typically be disabled. For large projects the javascript based search engine -# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. - -SEARCHENGINE = YES - -# When the SERVER_BASED_SEARCH tag is enabled the search engine will be -# implemented using a PHP enabled web server instead of at the web client -# using Javascript. Doxygen will generate the search PHP script and index -# file to put on the web server. The advantage of the server -# based approach is that it scales better to large projects and allows -# full text search. The disadvances is that it is more difficult to setup -# and does not have live searching capabilities. - -SERVER_BASED_SEARCH = NO - -#--------------------------------------------------------------------------- -# configuration options related to the LaTeX output -#--------------------------------------------------------------------------- - -# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will -# generate Latex output. - -GENERATE_LATEX = YES - -# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `latex' will be used as the default path. - -LATEX_OUTPUT = latex - -# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be -# invoked. If left blank `latex' will be used as the default command name. -# Note that when enabling USE_PDFLATEX this option is only used for -# generating bitmaps for formulas in the HTML output, but not in the -# Makefile that is written to the output directory. - -LATEX_CMD_NAME = latex - -# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to -# generate index for LaTeX. If left blank `makeindex' will be used as the -# default command name. - -MAKEINDEX_CMD_NAME = makeindex - -# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact -# LaTeX documents. This may be useful for small projects and may help to -# save some trees in general. - -COMPACT_LATEX = NO - -# The PAPER_TYPE tag can be used to set the paper type that is used -# by the printer. Possible values are: a4, a4wide, letter, legal and -# executive. If left blank a4wide will be used. - -PAPER_TYPE = a4wide - -# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX -# packages that should be included in the LaTeX output. - -EXTRA_PACKAGES = - -# The LATEX_HEADER tag can be used to specify a personal LaTeX header for -# the generated latex document. The header should contain everything until -# the first chapter. If it is left blank doxygen will generate a -# standard header. Notice: only use this tag if you know what you are doing! - -LATEX_HEADER = - -# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated -# is prepared for conversion to pdf (using ps2pdf). The pdf file will -# contain links (just like the HTML output) instead of page references -# This makes the output suitable for online browsing using a pdf viewer. - -PDF_HYPERLINKS = YES - -# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of -# plain latex in the generated Makefile. Set this option to YES to get a -# higher quality PDF documentation. - -USE_PDFLATEX = YES - -# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. -# command to the generated LaTeX files. This will instruct LaTeX to keep -# running if errors occur, instead of asking the user for help. -# This option is also used when generating formulas in HTML. - -LATEX_BATCHMODE = NO - -# If LATEX_HIDE_INDICES is set to YES then doxygen will not -# include the index chapters (such as File Index, Compound Index, etc.) -# in the output. - -LATEX_HIDE_INDICES = NO - -# If LATEX_SOURCE_CODE is set to YES then doxygen will include -# source code with syntax highlighting in the LaTeX output. -# Note that which sources are shown also depends on other settings -# such as SOURCE_BROWSER. - -LATEX_SOURCE_CODE = NO - -#--------------------------------------------------------------------------- -# configuration options related to the RTF output -#--------------------------------------------------------------------------- - -# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output -# The RTF output is optimized for Word 97 and may not look very pretty with -# other RTF readers or editors. - -GENERATE_RTF = NO - -# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `rtf' will be used as the default path. - -RTF_OUTPUT = rtf - -# If the COMPACT_RTF tag is set to YES Doxygen generates more compact -# RTF documents. This may be useful for small projects and may help to -# save some trees in general. - -COMPACT_RTF = NO - -# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated -# will contain hyperlink fields. The RTF file will -# contain links (just like the HTML output) instead of page references. -# This makes the output suitable for online browsing using WORD or other -# programs which support those fields. -# Note: wordpad (write) and others do not support links. - -RTF_HYPERLINKS = NO - -# Load stylesheet definitions from file. Syntax is similar to doxygen's -# config file, i.e. a series of assignments. You only have to provide -# replacements, missing definitions are set to their default value. - -RTF_STYLESHEET_FILE = - -# Set optional variables used in the generation of an rtf document. -# Syntax is similar to doxygen's config file. - -RTF_EXTENSIONS_FILE = - -#--------------------------------------------------------------------------- -# configuration options related to the man page output -#--------------------------------------------------------------------------- - -# If the GENERATE_MAN tag is set to YES (the default) Doxygen will -# generate man pages - -GENERATE_MAN = NO - -# The MAN_OUTPUT tag is used to specify where the man pages will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `man' will be used as the default path. - -MAN_OUTPUT = man - -# The MAN_EXTENSION tag determines the extension that is added to -# the generated man pages (default is the subroutine's section .3) - -MAN_EXTENSION = .3 - -# If the MAN_LINKS tag is set to YES and Doxygen generates man output, -# then it will generate one additional man file for each entity -# documented in the real man page(s). These additional files -# only source the real man page, but without them the man command -# would be unable to find the correct page. The default is NO. - -MAN_LINKS = NO - -#--------------------------------------------------------------------------- -# configuration options related to the XML output -#--------------------------------------------------------------------------- - -# If the GENERATE_XML tag is set to YES Doxygen will -# generate an XML file that captures the structure of -# the code including all documentation. - -GENERATE_XML = NO - -# The XML_OUTPUT tag is used to specify where the XML pages will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `xml' will be used as the default path. - -XML_OUTPUT = xml - -# The XML_SCHEMA tag can be used to specify an XML schema, -# which can be used by a validating XML parser to check the -# syntax of the XML files. - -XML_SCHEMA = - -# The XML_DTD tag can be used to specify an XML DTD, -# which can be used by a validating XML parser to check the -# syntax of the XML files. - -XML_DTD = - -# If the XML_PROGRAMLISTING tag is set to YES Doxygen will -# dump the program listings (including syntax highlighting -# and cross-referencing information) to the XML output. Note that -# enabling this will significantly increase the size of the XML output. - -XML_PROGRAMLISTING = YES - -#--------------------------------------------------------------------------- -# configuration options for the AutoGen Definitions output -#--------------------------------------------------------------------------- - -# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will -# generate an AutoGen Definitions (see autogen.sf.net) file -# that captures the structure of the code including all -# documentation. Note that this feature is still experimental -# and incomplete at the moment. - -GENERATE_AUTOGEN_DEF = NO - -#--------------------------------------------------------------------------- -# configuration options related to the Perl module output -#--------------------------------------------------------------------------- - -# If the GENERATE_PERLMOD tag is set to YES Doxygen will -# generate a Perl module file that captures the structure of -# the code including all documentation. Note that this -# feature is still experimental and incomplete at the -# moment. - -GENERATE_PERLMOD = NO - -# If the PERLMOD_LATEX tag is set to YES Doxygen will generate -# the necessary Makefile rules, Perl scripts and LaTeX code to be able -# to generate PDF and DVI output from the Perl module output. - -PERLMOD_LATEX = NO - -# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be -# nicely formatted so it can be parsed by a human reader. -# This is useful -# if you want to understand what is going on. -# On the other hand, if this -# tag is set to NO the size of the Perl module output will be much smaller -# and Perl will parse it just the same. - -PERLMOD_PRETTY = YES - -# The names of the make variables in the generated doxyrules.make file -# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. -# This is useful so different doxyrules.make files included by the same -# Makefile don't overwrite each other's variables. - -PERLMOD_MAKEVAR_PREFIX = - -#--------------------------------------------------------------------------- -# Configuration options related to the preprocessor -#--------------------------------------------------------------------------- - -# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will -# evaluate all C-preprocessor directives found in the sources and include -# files. - -ENABLE_PREPROCESSING = YES - -# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro -# names in the source code. If set to NO (the default) only conditional -# compilation will be performed. Macro expansion can be done in a controlled -# way by setting EXPAND_ONLY_PREDEF to YES. - -MACRO_EXPANSION = NO - -# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES -# then the macro expansion is limited to the macros specified with the -# PREDEFINED and EXPAND_AS_DEFINED tags. - -EXPAND_ONLY_PREDEF = NO - -# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files -# in the INCLUDE_PATH (see below) will be search if a #include is found. - -SEARCH_INCLUDES = YES - -# The INCLUDE_PATH tag can be used to specify one or more directories that -# contain include files that are not input files but should be processed by -# the preprocessor. - -INCLUDE_PATH = - -# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard -# patterns (like *.h and *.hpp) to filter out the header-files in the -# directories. If left blank, the patterns specified with FILE_PATTERNS will -# be used. - -INCLUDE_FILE_PATTERNS = - -# The PREDEFINED tag can be used to specify one or more macro names that -# are defined before the preprocessor is started (similar to the -D option of -# gcc). The argument of the tag is a list of macros of the form: name -# or name=definition (no spaces). If the definition and the = are -# omitted =1 is assumed. To prevent a macro definition from being -# undefined via #undef or recursively expanded use the := operator -# instead of the = operator. - -PREDEFINED = - -# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then -# this tag can be used to specify a list of macro names that should be expanded. -# The macro definition that is found in the sources will be used. -# Use the PREDEFINED tag if you want to use a different macro definition. - -EXPAND_AS_DEFINED = - -# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then -# doxygen's preprocessor will remove all function-like macros that are alone -# on a line, have an all uppercase name, and do not end with a semicolon. Such -# function macros are typically used for boiler-plate code, and will confuse -# the parser if not removed. - -SKIP_FUNCTION_MACROS = YES - -#--------------------------------------------------------------------------- -# Configuration::additions related to external references -#--------------------------------------------------------------------------- - -# The TAGFILES option can be used to specify one or more tagfiles. -# Optionally an initial location of the external documentation -# can be added for each tagfile. The format of a tag file without -# this location is as follows: -# -# TAGFILES = file1 file2 ... -# Adding location for the tag files is done as follows: -# -# TAGFILES = file1=loc1 "file2 = loc2" ... -# where "loc1" and "loc2" can be relative or absolute paths or -# URLs. If a location is present for each tag, the installdox tool -# does not have to be run to correct the links. -# Note that each tag file must have a unique name -# (where the name does NOT include the path) -# If a tag file is not located in the directory in which doxygen -# is run, you must also specify the path to the tagfile here. - -TAGFILES = - -# When a file name is specified after GENERATE_TAGFILE, doxygen will create -# a tag file that is based on the input files it reads. - -GENERATE_TAGFILE = - -# If the ALLEXTERNALS tag is set to YES all external classes will be listed -# in the class index. If set to NO only the inherited external classes -# will be listed. - -ALLEXTERNALS = NO - -# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed -# in the modules index. If set to NO, only the current project's groups will -# be listed. - -EXTERNAL_GROUPS = YES - -# The PERL_PATH should be the absolute path and name of the perl script -# interpreter (i.e. the result of `which perl'). - -PERL_PATH = /usr/bin/perl - -#--------------------------------------------------------------------------- -# Configuration options related to the dot tool -#--------------------------------------------------------------------------- - -# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will -# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base -# or super classes. Setting the tag to NO turns the diagrams off. Note that -# this option is superseded by the HAVE_DOT option below. This is only a -# fallback. It is recommended to install and use dot, since it yields more -# powerful graphs. - -CLASS_DIAGRAMS = YES - -# You can define message sequence charts within doxygen comments using the \msc -# command. Doxygen will then run the mscgen tool (see -# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the -# documentation. The MSCGEN_PATH tag allows you to specify the directory where -# the mscgen tool resides. If left empty the tool is assumed to be found in the -# default search path. - -MSCGEN_PATH = - -# If set to YES, the inheritance and collaboration graphs will hide -# inheritance and usage relations if the target is undocumented -# or is not a class. - -HIDE_UNDOC_RELATIONS = YES - -# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is -# available from the path. This tool is part of Graphviz, a graph visualization -# toolkit from AT&T and Lucent Bell Labs. The other options in this section -# have no effect if this option is set to NO (the default) - -HAVE_DOT = NO - -# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is -# allowed to run in parallel. When set to 0 (the default) doxygen will -# base this on the number of processors available in the system. You can set it -# explicitly to a value larger than 0 to get control over the balance -# between CPU load and processing speed. - -DOT_NUM_THREADS = 0 - -# By default doxygen will write a font called FreeSans.ttf to the output -# directory and reference it in all dot files that doxygen generates. This -# font does not include all possible unicode characters however, so when you need -# these (or just want a differently looking font) you can specify the font name -# using DOT_FONTNAME. You need need to make sure dot is able to find the font, -# which can be done by putting it in a standard location or by setting the -# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory -# containing the font. - -DOT_FONTNAME = FreeSans.ttf - -# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. -# The default size is 10pt. - -DOT_FONTSIZE = 10 - -# By default doxygen will tell dot to use the output directory to look for the -# FreeSans.ttf font (which doxygen will put there itself). If you specify a -# different font using DOT_FONTNAME you can set the path where dot -# can find it using this tag. - -DOT_FONTPATH = - -# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen -# will generate a graph for each documented class showing the direct and -# indirect inheritance relations. Setting this tag to YES will force the -# the CLASS_DIAGRAMS tag to NO. - -CLASS_GRAPH = YES - -# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen -# will generate a graph for each documented class showing the direct and -# indirect implementation dependencies (inheritance, containment, and -# class references variables) of the class with other documented classes. - -COLLABORATION_GRAPH = YES - -# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen -# will generate a graph for groups, showing the direct groups dependencies - -GROUP_GRAPHS = YES - -# If the UML_LOOK tag is set to YES doxygen will generate inheritance and -# collaboration diagrams in a style similar to the OMG's Unified Modeling -# Language. - -UML_LOOK = NO - -# If set to YES, the inheritance and collaboration graphs will show the -# relations between templates and their instances. - -TEMPLATE_RELATIONS = NO - -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT -# tags are set to YES then doxygen will generate a graph for each documented -# file showing the direct and indirect include dependencies of the file with -# other documented files. - -INCLUDE_GRAPH = YES - -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and -# HAVE_DOT tags are set to YES then doxygen will generate a graph for each -# documented header file showing the documented files that directly or -# indirectly include this file. - -INCLUDED_BY_GRAPH = YES - -# If the CALL_GRAPH and HAVE_DOT options are set to YES then -# doxygen will generate a call dependency graph for every global function -# or class method. Note that enabling this option will significantly increase -# the time of a run. So in most cases it will be better to enable call graphs -# for selected functions only using the \callgraph command. - -CALL_GRAPH = NO - -# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then -# doxygen will generate a caller dependency graph for every global function -# or class method. Note that enabling this option will significantly increase -# the time of a run. So in most cases it will be better to enable caller -# graphs for selected functions only using the \callergraph command. - -CALLER_GRAPH = NO - -# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen -# will graphical hierarchy of all classes instead of a textual one. - -GRAPHICAL_HIERARCHY = YES - -# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES -# then doxygen will show the dependencies a directory has on other directories -# in a graphical way. The dependency relations are determined by the #include -# relations between the files in the directories. - -DIRECTORY_GRAPH = YES - -# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images -# generated by dot. Possible values are png, jpg, or gif -# If left blank png will be used. - -DOT_IMAGE_FORMAT = png - -# The tag DOT_PATH can be used to specify the path where the dot tool can be -# found. If left blank, it is assumed the dot tool can be found in the path. - -DOT_PATH = - -# The DOTFILE_DIRS tag can be used to specify one or more directories that -# contain dot files that are included in the documentation (see the -# \dotfile command). - -DOTFILE_DIRS = - -# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of -# nodes that will be shown in the graph. If the number of nodes in a graph -# becomes larger than this value, doxygen will truncate the graph, which is -# visualized by representing a node as a red box. Note that doxygen if the -# number of direct children of the root node in a graph is already larger than -# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note -# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. - -DOT_GRAPH_MAX_NODES = 50 - -# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the -# graphs generated by dot. A depth value of 3 means that only nodes reachable -# from the root by following a path via at most 3 edges will be shown. Nodes -# that lay further from the root node will be omitted. Note that setting this -# option to 1 or 2 may greatly reduce the computation time needed for large -# code bases. Also note that the size of a graph can be further restricted by -# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. - -MAX_DOT_GRAPH_DEPTH = 0 - -# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent -# background. This is disabled by default, because dot on Windows does not -# seem to support this out of the box. Warning: Depending on the platform used, -# enabling this option may lead to badly anti-aliased labels on the edges of -# a graph (i.e. they become hard to read). - -DOT_TRANSPARENT = NO - -# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output -# files in one run (i.e. multiple -o and -T options on the command line). This -# makes dot run faster, but since only newer versions of dot (>1.8.10) -# support this, this feature is disabled by default. - -DOT_MULTI_TARGETS = YES - -# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will -# generate a legend page explaining the meaning of the various boxes and -# arrows in the dot generated graphs. - -GENERATE_LEGEND = YES - -# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will -# remove the intermediate dot files that are used to generate -# the various graphs. - -DOT_CLEANUP = YES diff --git a/drupal/islandora/include/admin.form.inc b/drupal/islandora/include/admin.form.inc deleted file mode 100644 index ce1d65920..000000000 --- a/drupal/islandora/include/admin.form.inc +++ /dev/null @@ -1,61 +0,0 @@ - array( - '#type' => 'textfield', - '#title' => t('Stomp URL'), - '#default_value' => variable_get('islandora_stomp_url', 'tcp://localhost:61613'), - '#description' => t('URL to the Stomp broker for async messaging'), - '#element_validate' => array('islandora_config_form_validate_stomp_url'), - '#required' => TRUE, - ), - 'islandora_triplestore_index_queue' => array( - '#type' => 'textfield', - '#title' => t('Triplestore Index Queue'), - '#default_value' => variable_get('islandora_triplestore_index_queue', 'islandora/triplestore/index'), - '#description' => t('Queue to send triplestore indexing messages'), - '#required' => TRUE, - ), - ); - - return system_settings_form($form); -} - -/** - * Stomp broker url validator. - * - * @param array $element - * Form element for stomp broker url. - * @param array $form_state - * Drupal form state. - * @param array $form - * Drupal renderable array. - */ -function islandora_config_form_validate_stomp_url(array $element, array &$form_state, array $form) { - // Try to connect to the server. - try { - $url = $element['#value']; - $stomp = new Stomp($url); - unset($stomp); - } - catch (StompException $e) { - form_error($element, t('Connection failed for @url: @message', array('@url' => $url, '@message' => $e->getMessage()))); - } -} diff --git a/drupal/islandora/include/fields.inc b/drupal/islandora/include/fields.inc deleted file mode 100644 index a1a8b8e09..000000000 --- a/drupal/islandora/include/fields.inc +++ /dev/null @@ -1,95 +0,0 @@ - array( - 'label' => 'Thumbnail', - 'description' => 'Thumbnail image', - ), - ISLANDORA_FEDORA_PATH_FIELD => array( - 'label' => 'Fedora Path', - 'description' => 'Path to resource in Fedora 4', - ), - ISLANDORA_FEDORA_HAS_PARENT_FIELD => array( - 'label' => 'fedora:hasParent', - 'description' => 'Parent resource in Fedora 4', - ), - ISLANDORA_PCDM_HAS_MEMBER_FIELD => array( - 'label' => 'pcdm:hasMember', - 'description' => 'Child resources in Fedora 4', - 'cardinality' => FIELD_CARDINALITY_UNLIMITED, - ), - ); - - // Iterate over fields and add each to the specified bundle. - foreach ($field_data as $field_name => $data) { - $field_label = $data['label']; - $field_description = $data['description']; - - islandora_add_field_to_bundle($bundle_name, $field_name, $field_label, $field_description); - } -} - -/** - * Adds a field to a bundle. - * - * @param string $bundle_name - * The machine name of the bundle. - * @param string $field_name - * The machine name of the field. - * @param string $field_label - * The human-readable label for the field. - * @param string $field_description - * The human-readable description for the field. - */ -function islandora_add_field_to_bundle($bundle_name, $field_name, $field_label, $field_description) { - // If this gets called from an install hook, we can't guarantee the t's - // existance. - $t = get_t(); - - if (field_info_field($field_name)) { - $field_instance = array( - 'field_name' => $field_name, - 'entity_type' => 'node', - 'bundle' => $bundle_name, - 'label' => $t("@label", array("@label" => $field_label)), - 'description' => $t("@description", array("@description" => $field_description)), - 'required' => FALSE, - ); - field_create_instance($field_instance); - $message = $t('Field @name was added to @bundle successfully', - array( - '@name' => $field_name, - '@bundle' => $bundle_name, - )); - drupal_set_message($message); - } -} - -/** - * Creates a field from a field definition. - * - * @param array $field_definition - * Field definition for the desired field. - */ -function islandora_create_field(array $field_definition) { - // If this gets called from an install hook, we can't guarantee the t's - // existance. - $t = get_t(); - - field_create_field($field_definition); - drupal_set_message($t("Created field @field", - array("@field" => $field_definition['field_name']))); -} diff --git a/drupal/islandora/include/rdf.inc b/drupal/islandora/include/rdf.inc deleted file mode 100644 index d360d46b1..000000000 --- a/drupal/islandora/include/rdf.inc +++ /dev/null @@ -1,21 +0,0 @@ - $rdf_model->ns)); - return $serializer->getSerializedIndex($rdf_model->index); -} diff --git a/drupal/islandora/include/rdf_mapping.inc b/drupal/islandora/include/rdf_mapping.inc deleted file mode 100644 index eed21cfe9..000000000 --- a/drupal/islandora/include/rdf_mapping.inc +++ /dev/null @@ -1,50 +0,0 @@ - 'node', - 'bundle' => $bundle, - 'mapping' => array( - 'rdftype' => $rdf_types, - 'uuid' => array( - 'predicates' => array('nfo:uuid'), - 'datatype' => 'xsd:string', - ), - ISLANDORA_FEDORA_HAS_PARENT_FIELD => array( - 'predicates' => array('fedora:hasParent'), - 'type' => 'rel', - ), - ISLANDORA_PCDM_HAS_MEMBER_FIELD => array( - 'predicates' => array('pcdm:hasMember'), - 'type' => 'rel', - ), - ), - ), - ); -} diff --git a/drupal/islandora/include/triplestore.inc b/drupal/islandora/include/triplestore.inc deleted file mode 100644 index 8a0b06051..000000000 --- a/drupal/islandora/include/triplestore.inc +++ /dev/null @@ -1,70 +0,0 @@ - $action, - 'Content-Type' => 'application/n-triples', - 'CamelFcrepoBaseUrl' => $base_url, - 'CamelFcrepoIdentifier' => "/node/{$node->nid}", - ); - - try { - $stomp = new Stomp($broker_url); - $stomp->send($queue, $msg, $headers); - unset($stomp); - return TRUE; - } - catch (StompException $e) { - watchdog('islandora', 'Error publishing triplestore index action to Stomp broker: @err', array('@err' => $e->getMessage()), WATCHDOG_ERROR); - return FALSE; - } -} diff --git a/drupal/islandora/include/utils.inc b/drupal/islandora/include/utils.inc deleted file mode 100644 index 15743c42f..000000000 --- a/drupal/islandora/include/utils.inc +++ /dev/null @@ -1,24 +0,0 @@ - array( - 'id' => 'MODS', - 'mimetype' => 'application/xml', - ), - ); -} diff --git a/drupal/islandora/islandora.info b/drupal/islandora/islandora.info deleted file mode 100644 index 3d7686297..000000000 --- a/drupal/islandora/islandora.info +++ /dev/null @@ -1,16 +0,0 @@ -name = Islandora -description = "View and manage Fedora 4 objects" -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = rest_server -dependencies[] = field_permissions -dependencies[] = field_readonly -dependencies[] = uuid_services -dependencies[] = views_ui -dependencies[] = rdfui -dependencies[] = xml_field -dependencies[] = xpath_field -dependencies[] = islandora_dc -dependencies[] = islandora_mods -dependencies[] = islandora_rdf_mapping_service diff --git a/drupal/islandora/islandora.install b/drupal/islandora/islandora.install deleted file mode 100644 index 8502a8476..000000000 --- a/drupal/islandora/islandora.install +++ /dev/null @@ -1,39 +0,0 @@ - ISLANDORA_TN_FIELD, - 'type' => 'image', - ), - array( - 'field_name' => ISLANDORA_FEDORA_PATH_FIELD, - 'type' => 'text', - ), - array( - 'field_name' => ISLANDORA_FEDORA_HAS_PARENT_FIELD, - 'type' => 'text', - ), - array( - 'field_name' => ISLANDORA_PCDM_HAS_MEMBER_FIELD, - 'type' => 'text', - 'cardinality' => FIELD_CARDINALITY_UNLIMITED, - ), - ); - - foreach ($fields as $field) { - islandora_create_field($field); - } -} diff --git a/drupal/islandora/islandora.module b/drupal/islandora/islandora.module deleted file mode 100644 index 91bf216b3..000000000 --- a/drupal/islandora/islandora.module +++ /dev/null @@ -1,263 +0,0 @@ - array( - 'title' => 'Islandora', - 'description' => 'Configure settings for Islandora', - 'page callback' => 'drupal_get_form', - 'page arguments' => array('islandora_config_form'), - 'file' => '/include/admin.form.inc', - 'access arguments' => array('administer site configuration'), - 'type' => MENU_NORMAL_ITEM, - ), - ); - return $items; -} - -/** - * Implements hook_ctools_plugin_api(). - */ -function islandora_ctools_plugin_api($owner, $api) { - if ($owner == 'services' && $api == 'services') { - return array( - 'version' => 3, - ); - } -} - -/** - * Implements hook_rdf_namespaces(). - */ -function islandora_rdf_namespaces() { - return array( - ISLANDORA_NAMESPACE_PREFIX => ISLANDORA_NAMESPACE, - ISLANDORA_RDF_NAMESPACE_PREFIX => ISLANDORA_RDF_NAMESPACE, - ISLANDORA_FEDORA_NAMESPACE_PREFIX => ISLANDORA_FEDORA_NAMESPACE, - ISLANDORA_PCDM_NAMESPACE_PREFIX => ISLANDORA_PCDM_NAMESPACE, - ISLANDORA_NFO_NAMESPACE_PREFIX => ISLANDORA_NFO_NAMESPACE, - ISLANDORA_NT_NAMESPACE_PREFIX => ISLANDORA_NT_NAMESPACE, - ISLANDORA_MIX_NAMESPACE_PREFIX => ISLANDORA_MIX_NAMESPACE, - ISLANDORA_LDP_NAMESPACE_PREFIX => ISLANDORA_LDP_NAMESPACE, - ); -} - -/** - * Implements hook_entity_load(). - */ -function islandora_entity_load($entities, $type) { - foreach ($entities as $entity) { - if (strcmp($type, "node") == 0) { - $entity->rdf_namespaces = rdf_get_namespaces(); - $entity->pcdm_file_mapping = module_invoke_all("pcdm_file_mapping"); - } - } -} - -/** - * Implements hook_node_postinsert(). - */ -function islandora_node_postinsert($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - $nodes = entity_uuid_load('node', array($node->uuid)); - - // Exit early if the node never was successfully inserted in the database. - if (empty($nodes)) { - return; - } - - $node = array_pop($nodes); - - module_load_include('inc', 'islandora', 'include/triplestore'); - islandora_triplestore_upsert($node); -} - -/** - * Implements hook_node_postupdate(). - */ -function islandora_node_postupdate($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Unfortunately, there's no way to tell if the db transaction got rolled - // back in this hook, so we'll default to doing it anyway so as not to miss - // any updates. Open to suggestions on this one. But we gotta do post_action - // hooks otherwise things can get crazy if the db transaction hasn't closed. - $nodes = entity_uuid_load('node', array($node->uuid)); - - // Exit early if something has gone wrong and there's no node info. - if (empty($nodes)) { - return; - } - - $node = array_pop($nodes); - - module_load_include('inc', 'islandora', 'include/triplestore'); - islandora_triplestore_upsert($node); -} - -/** - * Implements hook_node_postdelete(). - */ -function islandora_node_postdelete($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - module_load_include('inc', 'islandora', 'include/triplestore'); - islandora_triplestore_delete($node); -} - -/** - * Implements hook_default_services_endpoint(). - */ -function islandora_default_services_endpoint() { - $endpoint = new stdClass(); - $endpoint->disabled = FALSE; /* Edit this to true to make a default endpoint disabled initially */ - $endpoint->api_version = 3; - $endpoint->name = 'islandora'; - $endpoint->server = 'rest_server'; - $endpoint->path = 'islandora'; - $endpoint->authentication = array( - 'services' => 'services', - ); - $endpoint->server_settings = array( - 'formatters' => array( - 'json' => TRUE, - 'bencode' => FALSE, - 'jsonp' => FALSE, - 'php' => FALSE, - 'xml' => FALSE, - ), - 'parsers' => array( - 'application/json' => TRUE, - 'application/vnd.php.serialized' => FALSE, - 'application/x-www-form-urlencoded' => FALSE, - 'application/xml' => FALSE, - 'multipart/form-data' => FALSE, - 'text/xml' => FALSE, - ), - ); - $endpoint->resources = array( - 'medium_size' => array( - 'operations' => array( - 'create' => array( - 'enabled' => '1', - ), - ), - ), - 'node' => array( - 'operations' => array( - 'retrieve' => array( - 'enabled' => '1', - ), - 'update' => array( - 'enabled' => '1', - ), - 'delete' => array( - 'enabled' => '1', - ), - 'index' => array( - 'enabled' => '1', - ), - ), - 'relationships' => array( - 'files' => array( - 'enabled' => '1', - ), - 'comments' => array( - 'enabled' => '1', - ), - ), - 'targeted_actions' => array( - 'attach_file' => array( - 'enabled' => '1', - ), - ), - ), - 'rdf_mapping' => array( - 'operations' => array( - 'retrieve' => array( - 'enabled' => '1', - ), - ), - ), - 'system' => array( - 'actions' => array( - 'connect' => array( - 'enabled' => '1', - ), - ), - ), - 'tn' => array( - 'operations' => array( - 'create' => array( - 'enabled' => '1', - ), - ), - ), - 'user' => array( - 'actions' => array( - 'login' => array( - 'enabled' => '1', - 'settings' => array( - 'services' => array( - 'resource_api_version' => '1.0', - ), - ), - ), - 'logout' => array( - 'enabled' => '1', - 'settings' => array( - 'services' => array( - 'resource_api_version' => '1.0', - ), - ), - ), - 'token' => array( - 'enabled' => '1', - ), - ), - ), - ); - $endpoint->debug = 0; - return array($endpoint); -} diff --git a/drupal/islandora/tests/scripts/line_endings.sh b/drupal/islandora/tests/scripts/line_endings.sh deleted file mode 100755 index b72dde226..000000000 --- a/drupal/islandora/tests/scripts/line_endings.sh +++ /dev/null @@ -1,14 +0,0 @@ -#!/bin/bash - -RETURN=0 -FILES=`find -L $1 -name "*.info" -o -name "*.txt" -o -name "*.md"` -echo "Testing for files with DOS line endings..." -for FILE in $FILES -do - file $FILE | grep CRLF - if [ $? == 0 ] - then - RETURN=1 - fi -done -exit $RETURN diff --git a/drupal/islandora/tests/scripts/travis_setup.sh b/drupal/islandora/tests/scripts/travis_setup.sh deleted file mode 100755 index 6f9a946fb..000000000 --- a/drupal/islandora/tests/scripts/travis_setup.sh +++ /dev/null @@ -1,58 +0,0 @@ -#!/bin/bash -mysql -u root -e 'create database drupal;' -mysql -u root -e "GRANT ALL PRIVILEGES ON drupal.* To 'drupal'@'localhost' IDENTIFIED BY 'drupal';" - -# Java (Oracle) -sudo apt-get install -y software-properties-common -sudo apt-get install -y python-software-properties -sudo add-apt-repository -y ppa:webupd8team/java -sudo apt-get update -echo debconf shared/accepted-oracle-license-v1-1 select true | sudo debconf-set-selections -echo debconf shared/accepted-oracle-license-v1-1 seen true | sudo debconf-set-selections -sudo apt-get install -y oracle-java8-installer -sudo update-java-alternatives -s java-8-oracle -sudo apt-get install -y oracle-java8-set-default -export JAVA_HOME=/usr/lib/jvm/java-8-oracle - -cd $HOME -pear channel-discover pear.drush.org -pear upgrade --force Console_Getopt -pear upgrade --force pear -pear channel-discover pear.drush.org - -wget http://alpha.library.yorku.ca/drush-6.3.tar.gz -tar xf drush-6.3.tar.gz -sudo mv drush-6.3 /opt/ -sudo ln -s /opt/drush-6.3/drush /usr/bin/drush - -wget http://alpha.library.yorku.ca/PHP_CodeSniffer-1.5.6.tgz -pear install PHP_CodeSniffer-1.5.6.tgz - -wget http://alpha.library.yorku.ca/phpcpd.phar -sudo mv phpcpd.phar /usr/local/bin/phpcpd -sudo chmod +x /usr/local/bin/phpcpd - -phpenv rehash -drush dl --yes drupal -cd drupal-* -drush si minimal --db-url=mysql://drupal:drupal@localhost/drupal --yes -drush runserver --php-cgi=$HOME/.phpenv/shims/php-cgi localhost:8081 &>/tmp/drush_webserver.log & -ln -s $ISLANDORA_DIR sites/all/modules/islandora -drush dl --yes coder-7.x-2.4 -drush dl --yes potx-7.x-1.0 -drush en --yes coder_review -drush en --yes simpletest -drush en --yes potx -drush dl --user=1 services -drush en --user=1 --yes rest_server -drush en --user=1 --yes islandora -drush en --user=1 --yes islandora_apachesolr -drush en --user=1 --yes islandora_basic_image -drush en --user=1 --yes islandora_collection -drush en --user=1 --yes islandora_dc -drush en --user=1 --yes islandora_mods -drush en --user=1 --yes islandora_rdf_mapping_service -drush cc all -# The shebang in this file is a bogeyman that is haunting the web test cases. -rm /home/travis/.phpenv/rbenv.d/exec/hhvm-switcher.bash -sleep 20 diff --git a/drupal/islandora_apachesolr/islandora_apachesolr.info b/drupal/islandora_apachesolr/islandora_apachesolr.info deleted file mode 100644 index 8a365b6cb..000000000 --- a/drupal/islandora_apachesolr/islandora_apachesolr.info +++ /dev/null @@ -1,6 +0,0 @@ -name = Islandora Apache Solr Integration -description = A module which allows the Solr indexing and searching of Islandora resources. -core = 7.x -package = Islandora -dependencies[] = apachesolr -dependencies[] = uuid \ No newline at end of file diff --git a/drupal/islandora_apachesolr/islandora_apachesolr.module b/drupal/islandora_apachesolr/islandora_apachesolr.module deleted file mode 100644 index 8dc24f846..000000000 --- a/drupal/islandora_apachesolr/islandora_apachesolr.module +++ /dev/null @@ -1,14 +0,0 @@ - 0 && isset($entity->uuid)) { - $documents[0]->ss_uuid = $entity->uuid; - } -} diff --git a/drupal/islandora_basic_image/islandora_basic_image.info b/drupal/islandora_basic_image/islandora_basic_image.info deleted file mode 100644 index 024324fe7..000000000 --- a/drupal/islandora_basic_image/islandora_basic_image.info +++ /dev/null @@ -1,6 +0,0 @@ -name = Islandora Basic Image -description = "Content type, viewer, and hooks for Basic Image objects" -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = islandora diff --git a/drupal/islandora_basic_image/islandora_basic_image.install b/drupal/islandora_basic_image/islandora_basic_image.install deleted file mode 100644 index 2e7162687..000000000 --- a/drupal/islandora_basic_image/islandora_basic_image.install +++ /dev/null @@ -1,27 +0,0 @@ - ISLANDORA_BASIC_IMAGE_MEDIUM_SIZE_FIELD, - 'type' => 'image', - )); - islandora_add_field_to_bundle(ISLANDORA_BASIC_IMAGE_CONTENT_TYPE, ISLANDORA_BASIC_IMAGE_MEDIUM_SIZE_FIELD, "Medium Size", "A display copy of the image"); - -} diff --git a/drupal/islandora_basic_image/islandora_basic_image.module b/drupal/islandora_basic_image/islandora_basic_image.module deleted file mode 100644 index 196856b3d..000000000 --- a/drupal/islandora_basic_image/islandora_basic_image.module +++ /dev/null @@ -1,215 +0,0 @@ - array( - 'name' => t("Basic Image"), - 'base' => ISLANDORA_BASIC_IMAGE_CONTENT_TYPE, - 'description' => t("A Drupal node modeling a basic image pcdm:Object"), - ), - ); -} - -/** - * Implements hook_form(). - */ -function islandora_basic_image_form($node, array &$form_state) { - return node_content_form($node, $form_state); -} - -/** - * Implements hook_form_FORM_ID_alter(). - */ -function islandora_basic_image_form_islandora_basic_image_node_form_alter(&$form, array &$form_state, $form_id) { - $form['title']['#weight'] = -6; - $form['obj'] = array( - '#type' => 'file', - '#title' => t('Basic Image'), - '#description' => t('Upload your archival object to put in Fedora. This will generate new derivatives'), - '#weight' => -5, - ); - - // Add a collection picker if node is new (e.g. this is an insert form). - $node = $form_state['node']; - if (!isset($node->nid) || isset($node->is_new)) { - // Construct list of options from db and a default. - $from_db = db_select('node', 'n') - ->fields('n', array('uuid', 'title')) - ->condition('n.type', ISLANDORA_COLLECTION_CONTENT_TYPE) - ->execute() - ->fetchAllKeyed(); - - // Add the select to the form. - $form['parent_collection'] = array( - '#type' => 'select', - '#title' => t('Parent Collection'), - '#description' => t('Select the parent collection to add this to.'), - '#options' => $from_db, - '#weight' => -4, - '#required' => TRUE, - ); - - // Keep title on top. - $form['title']['#weight'] = -7; - - // Tack on a custom submit handler to attach data on the entity for use - // later on in the post action hooks. - array_unshift($form['#submit'], 'islandora_basic_image_add_parent_uuid'); - } -} - -/** - * Custom submit handler to pass along parent uuid. - * - * @param array $form - * Drupal form. - * @param array $form_state - * Drupal form state. - */ -function islandora_basic_image_add_parent_uuid(array $form, array &$form_state) { - $node = $form_state['node']; - $node->parent_collection = ""; - if (isset($form_state['values']['parent_collection'])) { - $form_state['values']['field_fedora_has_parent']['und'][0]['value'] = $form_state['values']['parent_collection']; - } -} - -/** - * Implements hook_rdf_mapping(). - */ -function islandora_basic_image_rdf_mapping() { - module_load_include('inc', 'islandora', 'include/rdf_mapping'); - $rdf_types = array( - ISLANDORA_PCDM_OBJECT_RDF_TYPE, - ISLANDORA_BASIC_IMAGE_RDF_TYPE, - ); - return islandora_get_default_rdf_mapping(ISLANDORA_BASIC_IMAGE_CONTENT_TYPE, $rdf_types); -} - -/** - * Implements hook_node_postinsert(). - */ -function islandora_basic_image_node_postinsert($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Exit early if it's not a basic_image. - if (strcmp($node->type, ISLANDORA_BASIC_IMAGE_CONTENT_TYPE) != 0) { - return; - } - - $parent_collection = $node->parent_collection; - - $nodes = entity_uuid_load('node', array($node->uuid)); - - // Exit early if the node never was successfully inserted in the database. - if (empty($nodes)) { - return; - } - - $node = array_pop($nodes); - - // Set the options for httprl. - $options = array( - 'method' => 'POST', - 'data' => array( - 'mimetype' => $_FILES['files']['type']['obj'], - 'node' => json_encode($node), - ), - ); - - // Add the obj file to the options if it exists. - $has_obj = isset($_FILES['files']['tmp_name']['obj']); - if ($has_obj) { - $options['data']['files'] = array( - 'obj' => array( - $_FILES['files']['tmp_name']['obj'], - ), - ); - } - - $url = "http://127.0.0.1:8181/cxf/islandora/image/$parent_collection"; - httprl_request($url, - $options); - $response = httprl_send_request(); -} - -/** - * Implements hook_node_postupdate(). - */ -function islandora_basic_image_node_postupdate($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Exit early if it's not a basic image. - if (strcmp($node->type, ISLANDORA_BASIC_IMAGE_CONTENT_TYPE) != 0) { - return; - } - - $nodes = entity_uuid_load('node', array($node->uuid)); - if (empty($nodes)) { - return; - } - $node = array_pop($nodes); - - // Set the options for httprl. - $options = array( - 'method' => 'PUT', - 'data' => array( - 'mimetype' => $_FILES['files']['type']['obj'], - 'node' => json_encode($node), - ), - ); - - // Add the obj file to the options if it exists. - $has_obj = isset($_FILES['files']['tmp_name']['obj']); - if ($has_obj) { - $options['data']['files'] = array( - 'obj' => array( - $_FILES['files']['tmp_name']['obj'], - ), - ); - } - - httprl_request("http://127.0.0.1:8181/cxf/islandora/image/{$node->uuid}", - $options); - $response = httprl_send_request(); -} - -/** - * Implements hook_node_postdelete(). - */ -function islandora_basic_image_node_postdelete($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Exit early if it's not a collection. - if (strcmp($node->type, ISLANDORA_BASIC_IMAGE_CONTENT_TYPE) != 0) { - return; - } - - $uuid = $node->uuid; - httprl_request("http://127.0.0.1:8181/cxf/islandora/image/$uuid", - array( - 'method' => 'DELETE', - )); - $response = httprl_send_request(); -} diff --git a/drupal/islandora_collection/include/islandora_collection.views_default.inc b/drupal/islandora_collection/include/islandora_collection.views_default.inc deleted file mode 100644 index a0cf7643e..000000000 --- a/drupal/islandora_collection/include/islandora_collection.views_default.inc +++ /dev/null @@ -1,78 +0,0 @@ -name = 'collection_view'; - $view->description = 'Shows all members of a collection'; - $view->tag = 'default'; - $view->base_table = 'node'; - $view->human_name = 'Collection View'; - $view->core = 7; - $view->api_version = '3.0'; - $view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */ - - /* Display: Master */ - $handler = $view->new_display('default', 'Master', 'default'); - $handler->display->display_options['title'] = 'Members'; - $handler->display->display_options['use_more_always'] = FALSE; - $handler->display->display_options['access']['type'] = 'perm'; - $handler->display->display_options['cache']['type'] = 'none'; - $handler->display->display_options['query']['type'] = 'views_query'; - $handler->display->display_options['exposed_form']['type'] = 'basic'; - $handler->display->display_options['pager']['type'] = 'full'; - $handler->display->display_options['pager']['options']['items_per_page'] = '10'; - $handler->display->display_options['style_plugin'] = 'default'; - $handler->display->display_options['row_plugin'] = 'node'; - /* Relationship: Content: Relation: pcdm:hasMember (node → node) */ - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['id'] = 'relation_pcdm_hasmember_node'; - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['table'] = 'node'; - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['field'] = 'relation_pcdm_hasmember_node'; - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['required'] = TRUE; - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['r_index'] = '1'; - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['entity_deduplication_left'] = 0; - $handler->display->display_options['relationships']['relation_pcdm_hasmember_node']['entity_deduplication_right'] = 0; - /* Field: Content: Title */ - $handler->display->display_options['fields']['title']['id'] = 'title'; - $handler->display->display_options['fields']['title']['table'] = 'node'; - $handler->display->display_options['fields']['title']['field'] = 'title'; - $handler->display->display_options['fields']['title']['label'] = ''; - $handler->display->display_options['fields']['title']['alter']['word_boundary'] = FALSE; - $handler->display->display_options['fields']['title']['alter']['ellipsis'] = FALSE; - /* Sort criterion: Content: Post date */ - $handler->display->display_options['sorts']['created']['id'] = 'created'; - $handler->display->display_options['sorts']['created']['table'] = 'node'; - $handler->display->display_options['sorts']['created']['field'] = 'created'; - $handler->display->display_options['sorts']['created']['order'] = 'DESC'; - /* Contextual filter: Content: Node UUID */ - $handler->display->display_options['arguments']['uuid']['id'] = 'uuid'; - $handler->display->display_options['arguments']['uuid']['table'] = 'node'; - $handler->display->display_options['arguments']['uuid']['field'] = 'uuid'; - $handler->display->display_options['arguments']['uuid']['relationship'] = 'relation_pcdm_hasmember_node'; - $handler->display->display_options['arguments']['uuid']['default_argument_type'] = 'fixed'; - $handler->display->display_options['arguments']['uuid']['summary']['number_of_records'] = '0'; - $handler->display->display_options['arguments']['uuid']['summary']['format'] = 'default_summary'; - $handler->display->display_options['arguments']['uuid']['summary_options']['items_per_page'] = '25'; - $handler->display->display_options['arguments']['uuid']['limit'] = '0'; - /* Filter criterion: Content: Published */ - $handler->display->display_options['filters']['status']['id'] = 'status'; - $handler->display->display_options['filters']['status']['table'] = 'node'; - $handler->display->display_options['filters']['status']['field'] = 'status'; - $handler->display->display_options['filters']['status']['value'] = 1; - $handler->display->display_options['filters']['status']['group'] = 1; - $handler->display->display_options['filters']['status']['expose']['operator'] = FALSE; - - /* Display: Page */ - $handler = $view->new_display('page', 'Page', 'page'); - $handler->display->display_options['path'] = 'collection-view/%'; - - $views[$view->name] = $view; - return $views; -} diff --git a/drupal/islandora_collection/include/relations.inc b/drupal/islandora_collection/include/relations.inc deleted file mode 100644 index eef1fcf04..000000000 --- a/drupal/islandora_collection/include/relations.inc +++ /dev/null @@ -1,35 +0,0 @@ -disabled = FALSE; /* Edit this to true to make a default relation_type disabled initially */ - $relation_type->api_version = 1; - $relation_type->relation_type = 'pcdm_hasmember'; - $relation_type->label = 'pcdm:hasMember'; - $relation_type->reverse_label = 'fedora:hasParent'; - $relation_type->directional = 1; - $relation_type->transitive = 0; - $relation_type->r_unique = 0; - $relation_type->min_arity = 2; - $relation_type->max_arity = 2; - $relation_type->source_bundles = array( - 0 => 'node:basic_image', - 1 => 'node:collection', - ); - $relation_type->target_bundles = array( - 0 => 'node:basic_image', - 1 => 'node:collection', - ); - // Relation type create adds default keys. It also handles casting to array. - $relation_type = relation_type_create($relation_type); - // Yes, in relation.module 'save' is a distinct step from 'create'. - relation_type_save($relation_type); -} diff --git a/drupal/islandora_collection/islandora_collection.info b/drupal/islandora_collection/islandora_collection.info deleted file mode 100644 index 5efc2e694..000000000 --- a/drupal/islandora_collection/islandora_collection.info +++ /dev/null @@ -1,8 +0,0 @@ -name = Islandora Collection -description = "Content type, view, and hooks for Collections" -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = islandora -dependencies[] = hook_post_action -dependencies[] = httprl diff --git a/drupal/islandora_collection/islandora_collection.install b/drupal/islandora_collection/islandora_collection.install deleted file mode 100644 index 7f5791cae..000000000 --- a/drupal/islandora_collection/islandora_collection.install +++ /dev/null @@ -1,20 +0,0 @@ - 3.0, - 'path' => drupal_get_path('module', 'islandora_collection') . '/include', - ); -} - -/** - * Implements hook_node_info(). - */ -function islandora_collection_node_info() { - return array( - ISLANDORA_COLLECTION_CONTENT_TYPE => array( - 'name' => t("Collection"), - 'base' => ISLANDORA_COLLECTION_CONTENT_TYPE, - 'description' => t("A Drupal node modeling a pcdm:Collection."), - ), - ); -} - -/** - * Implements hook_form(). - */ -function islandora_collection_form($node, array &$form_state) { - return node_content_form($node, $form_state); -} - -/** - * Implements hook_form_FORM_ID_alter(). - */ -function islandora_collection_form_islandora_collection_node_form_alter(&$form, array &$form_state, $form_id) { - $node = $form_state['node']; - - // Add a collection picker if node is new (e.g. this is an insert form). - if (!isset($node->nid) || isset($node->is_new)) { - // Construct list of options from db and a default. - $default = array('' => t('Fedora Root')); - $from_db = db_select('node', 'n') - ->fields('n', array('uuid', 'title')) - ->condition('n.type', ISLANDORA_COLLECTION_CONTENT_TYPE) - ->execute() - ->fetchAllKeyed(); - $options = $default + $from_db; - - // Add the select to the form. - $form['parent_collection'] = array( - '#type' => 'select', - '#title' => t('Parent Collection'), - '#description' => t('Select the parent collection to add this to. Select "Fedora Root" if you want it to be a top-level collection'), - '#options' => $options, - '#default_value' => '', - '#weight' => -4, - ); - - // Keep title on top. - $form['title']['#weight'] = -5; - - // Tack on a custom submit handler to attach data on the entity for use - // later on in the post action hooks. - array_unshift($form['#submit'], 'islandora_collection_add_parent_uuid'); - } -} - -/** - * Custom submit handler to pass along parent uuid. - * - * @param array $form - * Drupal form. - * @param array $form_state - * Drupal form state. - */ -function islandora_collection_add_parent_uuid(array $form, array &$form_state) { - $node = $form_state['node']; - $node->parent_collection = ""; - if (isset($form_state['parent_collection']['#value'])) { - $node->parent_collection = $form_state['parent_collection']['#value']; - } -} - -/** - * Implements hook_rdf_mapping(). - */ -function islandora_collection_rdf_mapping() { - module_load_include('inc', 'islandora', 'include/rdf_mapping'); - $rdf_types = array( - ISLANDORA_PCDM_COLLECTION_RDF_TYPE, - ISLANDORA_COLLECTION_RDF_TYPE, - ); - return islandora_get_default_rdf_mapping(ISLANDORA_COLLECTION_CONTENT_TYPE, $rdf_types); -} - -/** - * Implements hook_node_postinsert(). - */ -function islandora_collection_node_postinsert($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Exit early if it's not a collection. - if (strcmp($node->type, ISLANDORA_COLLECTION_CONTENT_TYPE) != 0) { - return; - } - - $parent_collection = $node->parent_collection; - $nodes = entity_uuid_load('node', array($node->uuid)); - - // Exit early if the node never was successfully inserted in the database. - if (empty($nodes)) { - return; - } - - $node = array_pop($nodes); - $url = "http://127.0.0.1:8181/cxf/islandora/collection/$parent_collection"; - - // Don't forget the trailing slash. - httprl_request($url, - array( - 'method' => 'POST', - 'headers' => array( - 'Content-Type' => 'application/json', - ), - 'data' => json_encode($node), - )); - $response = httprl_send_request(); -} - -/** - * Implements hook_node_postupdate(). - */ -function islandora_collection_node_postupdate($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Exit early if it's not a collection. - if (strcmp($node->type, ISLANDORA_COLLECTION_CONTENT_TYPE) != 0) { - return; - } - - // Unfortunately, there's no way to tell if the db transaction got rolled - // back in this hook, so we'll default to doing it anyway so as not to miss - // any updates. Open to suggestions on this one. But we gotta do post_action - // hooks otherwise things can get crazy if the db transaction hasn't closed. - $nodes = entity_uuid_load('node', array($node->uuid)); - - // Exit early if something has gone wrong and there's no node info. - if (empty($nodes)) { - return; - } - - $node = array_pop($nodes); - $uuid = $node->uuid; - httprl_request("http://127.0.0.1:8181/cxf/islandora/collection/$uuid", - array( - 'method' => 'PUT', - 'headers' => array( - 'Content-Type' => 'application/json', - ), - 'data' => json_encode($node), - )); - $response = httprl_send_request(); -} - -/** - * Implements hook_node_postdelete(). - */ -function islandora_collection_node_postdelete($node) { - module_load_include('inc', 'islandora', 'include/utils'); - if (islandora_ignore_hooks()) { - return; - } - - // Exit early if it's not a collection. - if (strcmp($node->type, ISLANDORA_COLLECTION_CONTENT_TYPE) != 0) { - return; - } - - $uuid = $node->uuid; - httprl_request("http://127.0.0.1:8181/cxf/islandora/collection/$uuid", - array( - 'method' => 'DELETE', - )); - $response = httprl_send_request(); -} diff --git a/drupal/islandora_dc/include/fields.inc b/drupal/islandora_dc/include/fields.inc deleted file mode 100644 index 8e7e6d74e..000000000 --- a/drupal/islandora_dc/include/fields.inc +++ /dev/null @@ -1,88 +0,0 @@ - array( - 'label' => 'DC Contributor', - 'description' => 'Dublin Core 1.1 Contributor Metadata', - ), - ISLANDORA_DC_COVERAGE_FIELD => array( - 'label' => 'DC Coverage', - 'description' => 'Dublin Core 1.1 Coverage Metadata', - ), - ISLANDORA_DC_CREATOR_FIELD => array( - 'label' => 'DC Creator', - 'description' => 'Dublin Core 1.1 Creator Metadata', - ), - ISLANDORA_DC_DATE_FIELD => array( - 'label' => 'DC Date', - 'description' => 'Dublin Core 1.1 Date Metadata', - ), - ISLANDORA_DC_DESCRIPTION_FIELD => array( - 'label' => 'DC Description', - 'description' => 'Dublin Core 1.1 Description Metadata', - ), - ISLANDORA_DC_FORMAT_FIELD => array( - 'label' => 'DC Format', - 'description' => 'Dublin Core 1.1 Format Metadata', - ), - ISLANDORA_DC_IDENTIFIER_FIELD => array( - 'label' => 'DC Identifier', - 'description' => 'Dublin Core 1.1 Identifier Metadata', - ), - ISLANDORA_DC_LANGUAGE_FIELD => array( - 'label' => 'DC Language', - 'description' => 'Dublin Core 1.1 Language Metadata', - ), - ISLANDORA_DC_PUBLISHER_FIELD => array( - 'label' => 'DC Publisher', - 'description' => 'Dublin Core 1.1 Publisher Metadata', - ), - ISLANDORA_DC_RELATION_FIELD => array( - 'label' => 'DC Relation', - 'description' => 'Dublin Core 1.1 Relation Metadata', - ), - ISLANDORA_DC_RIGHTS_FIELD => array( - 'label' => 'DC Rights', - 'description' => 'Dublin Core 1.1 Rights Metadata', - ), - ISLANDORA_DC_SOURCE_FIELD => array( - 'label' => 'DC Source', - 'description' => 'Dublin Core 1.1 Source Metadata', - ), - ISLANDORA_DC_SUBJECT_FIELD => array( - 'label' => 'DC Subject', - 'description' => 'Dublin Core 1.1 Subject Metadata', - ), - ISLANDORA_DC_TITLE_FIELD => array( - 'label' => 'DC Title', - 'description' => 'Dublin Core 1.1 Title Metadata', - ), - ISLANDORA_DC_TYPE_FIELD => array( - 'label' => 'DC Type', - 'description' => 'Dublin Core 1.1 Type Metadata', - ), - ); - - // Iterate over fields and add each to the specified bundle. - foreach ($field_data as $field_name => $data) { - $field_label = $data['label']; - $field_description = $data['description']; - - islandora_add_field_to_bundle($bundle_name, $field_name, $field_label, $field_description); - } -} diff --git a/drupal/islandora_dc/islandora_dc.info b/drupal/islandora_dc/islandora_dc.info deleted file mode 100644 index 4212efa91..000000000 --- a/drupal/islandora_dc/islandora_dc.info +++ /dev/null @@ -1,5 +0,0 @@ -name = Islandora DC -description = "Fields and utilities for managing DC 1.1 metadata in Islandora" -package = Islandora -version = 7.x-dev -core = 7.x diff --git a/drupal/islandora_dc/islandora_dc.install b/drupal/islandora_dc/islandora_dc.install deleted file mode 100644 index e286f2de5..000000000 --- a/drupal/islandora_dc/islandora_dc.install +++ /dev/null @@ -1,42 +0,0 @@ - $field_name, - 'type' => 'text_long', - 'cardinality' => FIELD_CARDINALITY_UNLIMITED, - )); - } - -} diff --git a/drupal/islandora_dc/islandora_dc.module b/drupal/islandora_dc/islandora_dc.module deleted file mode 100644 index f3cd6c7cf..000000000 --- a/drupal/islandora_dc/islandora_dc.module +++ /dev/null @@ -1,33 +0,0 @@ - ISLANDORA_DC_NAMESPACE, - ); -} diff --git a/drupal/islandora_delete_by_fedora_uri_service/include/islandora_delete_by_fedora_uri_service.inc b/drupal/islandora_delete_by_fedora_uri_service/include/islandora_delete_by_fedora_uri_service.inc deleted file mode 100644 index 0c2e9a886..000000000 --- a/drupal/islandora_delete_by_fedora_uri_service/include/islandora_delete_by_fedora_uri_service.inc +++ /dev/null @@ -1,42 +0,0 @@ -fieldCondition('field_fedora_path', 'value', $fedora_uri) - ->execute(); - - // Delete 'em all. - foreach ($results as $entity_type => $entities) { - $ids = array_keys($entities); - if (entity_delete_multiple($entity_type, $ids) === FALSE) { - $response[] = "Could not delete any $entity_type identified by $fedora_uri."; - } - else { - $response[] = "Deleted entities of type $entity_type with ids " . implode(', ', $ids) . "."; - } - } - - if (!isset($response)) { - $response[] = "Could not find any entities identified by $fedora_uri."; - } - - return $response; -} diff --git a/drupal/islandora_delete_by_fedora_uri_service/islandora_delete_by_fedora_uri_service.info b/drupal/islandora_delete_by_fedora_uri_service/islandora_delete_by_fedora_uri_service.info deleted file mode 100644 index 3c1d5a488..000000000 --- a/drupal/islandora_delete_by_fedora_uri_service/islandora_delete_by_fedora_uri_service.info +++ /dev/null @@ -1,6 +0,0 @@ -name = Islandora Delete By Fedora URI Service -description = "Deletes Drupal nodes by Fedora URI. Needed for Sync to handle delete events that don't originate from Drupal." -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = rest_server diff --git a/drupal/islandora_delete_by_fedora_uri_service/islandora_delete_by_fedora_uri_service.module b/drupal/islandora_delete_by_fedora_uri_service/islandora_delete_by_fedora_uri_service.module deleted file mode 100644 index 6b234b355..000000000 --- a/drupal/islandora_delete_by_fedora_uri_service/islandora_delete_by_fedora_uri_service.module +++ /dev/null @@ -1,48 +0,0 @@ - array( - 'title' => t('Delete by Fedora URI.'), - 'description' => t('Allows external sources to delete Drupal nodes by Fedora URI.'), - ), - ); -} - -/** - * Implements hook_services_resources(). - */ -function islandora_delete_by_fedora_uri_service_services_resources() { - return array( - 'delete_by_fedora_uri' => array( - 'create' => array( - 'help' => t('Deletes a Drupal node by the Fedora URI supplied in the POST data.'), - 'file' => array( - 'type' => 'inc', - 'module' => 'islandora_delete_by_fedora_uri_service', - 'name' => 'include/islandora_delete_by_fedora_uri_service', - ), - 'callback' => 'islandora_delete_by_fedora_uri_service_delete', - 'access callback' => 'user_access', - 'access arguments' => array('islandora delete by fedora uri'), - 'args' => array( - array( - 'name' => 'args', - 'type' => 'array', - 'description' => t("JSON data containing arguments to the delete function (e.g. the Fedora URI)"), - 'source' => 'data', - 'optional' => FALSE, - ), - ), - ), - ), - ); -} diff --git a/drupal/islandora_medium_size_service/include/islandora_medium_size_service.inc b/drupal/islandora_medium_size_service/include/islandora_medium_size_service.inc deleted file mode 100644 index 831506fdd..000000000 --- a/drupal/islandora_medium_size_service/include/islandora_medium_size_service.inc +++ /dev/null @@ -1,50 +0,0 @@ -field_medium_size[LANGUAGE_NONE][] = array( - 'fid' => $file->fid, - 'alt' => "Medium sized image for node $uuid", - 'title' => "Medium sized image for node $uuid", - ); - $node->field_tn[LANGUAGE_NONE][] = array( - 'fid' => $file->fid, - 'width' => 100, - 'height' => 100, - 'alt' => "Thumbnail for node $uuid", - 'title' => "Thumbnail for node $uuid", - ); - - node_save($node); - - return "Successfully added medium sized image to node $uuid"; -} diff --git a/drupal/islandora_medium_size_service/islandora_medium_size_service.info b/drupal/islandora_medium_size_service/islandora_medium_size_service.info deleted file mode 100644 index cb6027fa0..000000000 --- a/drupal/islandora_medium_size_service/islandora_medium_size_service.info +++ /dev/null @@ -1,6 +0,0 @@ -name = Islandora Medium Size Service -description = "Adds medium size images to nodes" -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = rest_server diff --git a/drupal/islandora_medium_size_service/islandora_medium_size_service.module b/drupal/islandora_medium_size_service/islandora_medium_size_service.module deleted file mode 100644 index 6b5319b89..000000000 --- a/drupal/islandora_medium_size_service/islandora_medium_size_service.module +++ /dev/null @@ -1,48 +0,0 @@ - array( - 'title' => t('Add Medium Size'), - 'description' => t('Allows external sources to add medium size images to nodes.'), - ), - ); -} - -/** - * Implements hook_services_resources(). - */ -function islandora_medium_size_service_services_resources() { - return array( - 'medium_size' => array( - 'create' => array( - 'help' => t('Adds a medium sized image to the node identified by UUID.'), - 'file' => array( - 'type' => 'inc', - 'module' => 'islandora_medium_size_service', - 'name' => 'include/islandora_medium_size_service', - ), - 'callback' => 'islandora_medium_size_service_create', - 'access callback' => 'user_access', - 'access arguments' => array('islandora medium size service create'), - 'args' => array( - array( - 'name' => 'args', - 'type' => 'array', - 'description' => t("JSON data containing arguments to add the medium sized image."), - 'source' => 'data', - 'optional' => FALSE, - ), - ), - ), - ), - ); -} diff --git a/drupal/islandora_mods/include/fields.inc b/drupal/islandora_mods/include/fields.inc deleted file mode 100644 index 0aa454963..000000000 --- a/drupal/islandora_mods/include/fields.inc +++ /dev/null @@ -1,17 +0,0 @@ - ISLANDORA_MODS_FIELD, - 'type' => 'xml_field_xml', - )); -} diff --git a/drupal/islandora_mods/islandora_mods.module b/drupal/islandora_mods/islandora_mods.module deleted file mode 100644 index 4dd43bb0c..000000000 --- a/drupal/islandora_mods/islandora_mods.module +++ /dev/null @@ -1,34 +0,0 @@ - ISLANDORA_MODS_RDF_NAMESPACE, - ); -} - -/** - * Implements hook_pcdm_file_mapping(). - */ -function islandora_mods_pcdm_file_mapping() { - return array( - ISLANDORA_MODS_FIELD => array( - 'id' => ISLANDORA_MODS_FILE_ID, - 'mimetype' => 'application/xml', - ), - ); -} diff --git a/drupal/islandora_rdf_mapping_service/include/islandora_rdf_mapping_service.inc b/drupal/islandora_rdf_mapping_service/include/islandora_rdf_mapping_service.inc deleted file mode 100644 index 163d40c59..000000000 --- a/drupal/islandora_rdf_mapping_service/include/islandora_rdf_mapping_service.inc +++ /dev/null @@ -1,25 +0,0 @@ - rdf_mapping_load($type, $bundle), - 'rdf_namespaces' => rdf_get_namespaces(), - 'pcdm_file_mapping' => module_invoke_all('pcdm_file_mapping'), - ); -} diff --git a/drupal/islandora_rdf_mapping_service/islandora_rdf_mapping_service.info b/drupal/islandora_rdf_mapping_service/islandora_rdf_mapping_service.info deleted file mode 100644 index 08490b108..000000000 --- a/drupal/islandora_rdf_mapping_service/islandora_rdf_mapping_service.info +++ /dev/null @@ -1,6 +0,0 @@ -name = Islandora RDF Mapping Service -description = "Exposes RDF -> Field mapping for the middleware layer to use." -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = rest_server diff --git a/drupal/islandora_rdf_mapping_service/islandora_rdf_mapping_service.module b/drupal/islandora_rdf_mapping_service/islandora_rdf_mapping_service.module deleted file mode 100644 index 5c039c356..000000000 --- a/drupal/islandora_rdf_mapping_service/islandora_rdf_mapping_service.module +++ /dev/null @@ -1,59 +0,0 @@ - array( - 'title' => t('Retrieve RDF Mappings'), - 'description' => t('Allows external sources to request RDF mappings.'), - ), - ); -} - -/** - * Implements hook_services_resources(). - */ -function islandora_rdf_mapping_service_services_resources() { - return array( - 'rdf_mapping' => array( - 'retrieve' => array( - 'help' => t('Retrieves an RDF mapping using the supplied entity type and bundle.'), - 'file' => array( - 'type' => 'inc', - 'module' => 'islandora_rdf_mapping_service', - 'name' => 'include/islandora_rdf_mapping_service', - ), - 'callback' => 'islandora_rdf_mapping_service_retrieve', - 'access callback' => 'user_access', - 'access arguments' => array('islandora rdf mapping service retrieve'), - 'args' => array( - array( - 'name' => 'type', - 'type' => 'string', - 'description' => t("Entity type to which the RDF mapping belongs."), - 'source' => array( - 'path' => 0, - ), - 'optional' => FALSE, - ), - array( - 'name' => 'bundle', - 'type' => 'string', - 'description' => t("Bundle to which the RDF mapping belongs."), - 'source' => array( - 'path' => 1, - ), - 'optional' => FALSE, - ), - ), - ), - ), - ); -} diff --git a/drupal/islandora_tn_service/include/islandora_tn_service.inc b/drupal/islandora_tn_service/include/islandora_tn_service.inc deleted file mode 100644 index 68f33391e..000000000 --- a/drupal/islandora_tn_service/include/islandora_tn_service.inc +++ /dev/null @@ -1,45 +0,0 @@ -field_tn[LANGUAGE_NONE][] = array( - 'fid' => $file->fid, - 'width' => 100, - 'height' => 100, - 'alt' => "Thumbnail for node $uuid", - 'title' => "Thumbnail for node $uuid", - ); - - node_save($node); - - return "Successfully added thumbnail to node $uuid"; -} diff --git a/drupal/islandora_tn_service/islandora_tn_service.info b/drupal/islandora_tn_service/islandora_tn_service.info deleted file mode 100644 index 53d6a30b7..000000000 --- a/drupal/islandora_tn_service/islandora_tn_service.info +++ /dev/null @@ -1,6 +0,0 @@ -name = Islandora TN Service -description = "Adds thumbnail images to nodes" -package = Islandora -version = 7.x-dev -core = 7.x -dependencies[] = rest_server diff --git a/drupal/islandora_tn_service/islandora_tn_service.module b/drupal/islandora_tn_service/islandora_tn_service.module deleted file mode 100644 index e749254a9..000000000 --- a/drupal/islandora_tn_service/islandora_tn_service.module +++ /dev/null @@ -1,48 +0,0 @@ - array( - 'title' => t('Add Thumbnails'), - 'description' => t('Allows external sources to add thumbnails to nodes.'), - ), - ); -} - -/** - * Implements hook_services_resources(). - */ -function islandora_tn_service_services_resources() { - return array( - 'tn' => array( - 'create' => array( - 'help' => t('Adds a thumbnail to the node identified by UUID.'), - 'file' => array( - 'type' => 'inc', - 'module' => 'islandora_tn_service', - 'name' => 'include/islandora_tn_service', - ), - 'callback' => 'islandora_tn_service_create', - 'access callback' => 'user_access', - 'access arguments' => array('islandora tn service create'), - 'args' => array( - array( - 'name' => 'args', - 'type' => 'array', - 'description' => t("JSON data containing arguments to add the thumbnail."), - 'source' => 'data', - 'optional' => FALSE, - ), - ), - ), - ), - ); -}