You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(15) |
Dec
(13) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(145) |
Feb
(2) |
Mar
(123) |
Apr
(178) |
May
(30) |
Jun
(56) |
Jul
|
Aug
(18) |
Sep
(6) |
Oct
(9) |
Nov
|
Dec
(8) |
| 2004 |
Jan
(16) |
Feb
(3) |
Mar
(12) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(12) |
Nov
(27) |
Dec
(20) |
| 2006 |
Jan
(17) |
Feb
(46) |
Mar
(87) |
Apr
(63) |
May
(25) |
Jun
(3) |
Jul
|
Aug
(21) |
Sep
(47) |
Oct
(9) |
Nov
(3) |
Dec
|
| 2007 |
Jan
(27) |
Feb
(4) |
Mar
(6) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: John W. <jwe...@us...> - 2007-06-14 21:28:02
|
Update of /cvsroot/dlese/oai-project In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv21743 Modified Files: build.xml Log Message: added joai.properties lookup Index: build.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/build.xml,v retrieving revision 1.70 retrieving revision 1.71 diff -C2 -r1.70 -r1.71 *** build.xml 19 Mar 2007 18:12:04 -0000 1.70 --- build.xml 14 Jun 2007 21:27:58 -0000 1.71 *************** *** 86,90 **** --> ! <!-- Search for properties defined in this order: --> <property file="../dpc.properties"/> <property file="${user.home}/build.properties"/> --- 86,91 ---- --> ! <!-- Search for properties defined in this order: --> ! <property file="../joai.properties"/> <property file="../dpc.properties"/> <property file="${user.home}/build.properties"/> |
|
From: John W. <jwe...@us...> - 2007-06-07 23:45:37
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv19194/web/docs Modified Files: LICENSE.txt Added Files: COPYRIGHT.txt Log Message: updated copyright and license --- NEW FILE --- Copyright 2002 - 2007 DLESE Program Center, University Corporation for Atmospheric Research (UCAR), P.O. Box 3000, Boulder, CO 80307. When using, modifying or redistributing this software, please include the following acknowledgment: "This product includes software developed by the University Corporation for Atmospheric Research (http://www.ucar.edu/), DLESE Program Center." This software 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; Version 2 of the License. This software 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 software; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Index: LICENSE.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/LICENSE.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** LICENSE.txt 30 May 2006 23:05:21 -0000 1.2 --- LICENSE.txt 7 Jun 2007 23:45:34 -0000 1.3 *************** *** 56,60 **** The precise terms and conditions for copying, distribution and modification follow. ! GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION --- 56,60 ---- The precise terms and conditions for copying, distribution and modification follow. ! GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION *************** *** 111,115 **** does not normally print such an announcement, your work based on the Program is not required to print an announcement.) ! These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, --- 111,115 ---- does not normally print such an announcement, your work based on the Program is not required to print an announcement.) ! These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, *************** *** 169,173 **** distribution of the source code, even though third parties are not compelled to copy the source along with the object code. ! 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt --- 169,173 ---- distribution of the source code, even though third parties are not compelled to copy the source along with the object code. ! 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt *************** *** 226,230 **** This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. ! 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the --- 226,230 ---- This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. ! 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the *************** *** 279,283 **** END OF TERMS AND CONDITIONS ! How to Apply These Terms to Your New Programs --- 279,283 ---- END OF TERMS AND CONDITIONS ! How to Apply These Terms to Your New Programs |
|
From: John W. <jwe...@us...> - 2007-06-04 17:51:12
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv14035/web/docs Modified Files: CHANGES.txt faq.jsp Log Message: updated the FAQ Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.39 retrieving revision 1.40 diff -C2 -r1.39 -r1.40 *** CHANGES.txt 20 Mar 2007 21:47:38 -0000 1.39 --- CHANGES.txt 4 Jun 2007 17:51:08 -0000 1.40 *************** *** 6,9 **** --- 6,14 ---- + v3.0.11 + + -Added more documentation in the FAQ + + v3.0.10 (Released March 20, 2007) Index: faq.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/faq.jsp,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -r1.3 -r1.4 *** faq.jsp 19 Mar 2007 18:12:04 -0000 1.3 --- faq.jsp 4 Jun 2007 17:51:08 -0000 1.4 *************** *** 163,166 **** --- 163,177 ---- <p><strong>Is it possible to customize the CSS, HTML or other features of the jOAI user interface?</strong></p> <p>Yes. jOAI is rendered using CSS, HTML (which is generated by JSP), and JavaScript. Simply modify the .css, .jsp or .js files as desired to change the look-and-feel of the application. Tip: The struts-config.xml file found in WEB-INF describes what .jsp files are used to render certain portions of the application. The file head.jsp defines what items appear in the jOAI menus.</p> + <p><strong>When upgrading from a previous version of jOAI, is it possible to preserve the settings, indexes and files for the data provider and harvester?</strong></p> + <p>Yes. When upgrading jOAI since version 3.0.2, it is possible to preserve the previous settings, indexes and files.</p> + <p>Follow these steps:</p> + <p>1. Stop Tomcat</p> + <p>2. Move and save the current oai installation to a location outside the webapps directory. (Backup and save a copy).</p> + <p>3. Install the new version of jOAI (put oai.war in webapps, start Tomcat, etc). Tomcat will unpack the new oai.war file.</p> + <p>Then, to restore the previous settings, indexes and files:</p> + <p>4. Stop tomcat again.</p> + <p>5. In the new webapps/oai/WEB-INF directory, replace the two directories 'repository_settings_and_data' and 'harvester_settings_and_data' with the ones saved from the previous installation.</p> + <p>6. Start Tomcat.</p> + <p>7. Visit the jOAI admin and search pages to confirm that the settings and indexes have been preserved for the data provider and harvester.</p> <p><strong>Can jOAI be configured to run through an Apache web server (httpd)?</strong></p> <p>Yes. Running jOAI through an <a href="http://httpd.apache.org/">Apache web |
|
From: John W. <jwe...@us...> - 2007-05-04 23:37:13
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv28703/web/docs Modified Files: oai-documentation.html Log Message: updated documentation for library v2.5 Index: oai-documentation.html =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/oai-documentation.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** oai-documentation.html 12 Oct 2006 23:32:25 -0000 1.2 --- oai-documentation.html 4 May 2007 23:37:08 -0000 1.3 *************** *** 6,11 **** <h1> Documentation for the <a href="http://www.dlese.org/oai/index.jsp">jOAI Software</a></h1> ! <h2> Version 3.0.6</h2> ! OAI v3.0.6 corresponds to DLESE v2.4 <h2> Description </h2> <p>The jOAI software includes a data provider that supports the <a href="http://www.openarchives.org">Open --- 6,10 ---- <h1> Documentation for the <a href="http://www.dlese.org/oai/index.jsp">jOAI Software</a></h1> ! <h2> Version 3.0.10</h2> <h2> Description </h2> <p>The jOAI software includes a data provider that supports the <a href="http://www.openarchives.org">Open *************** *** 66,71 **** Java, J2EE, Struts, Lucene, Tomcat, Dom4j, JSTL tag libraries. <h2> Development process and workflow </h2> ! <p>See the <a href="../../dds-project/docs/software-development-process.html">development ! process documentation</a> for details on how the software is developed and deployed.</p> <h3>Release deployment process</h3> --- 65,70 ---- Java, J2EE, Struts, Lucene, Tomcat, Dom4j, JSTL tag libraries. <h2> Development process and workflow </h2> ! <p>See the development ! process documentation for details on how the software is developed and deployed.</p> <h3>Release deployment process</h3> *************** *** 73,95 **** communities as an out-of-the-box OAI solution. The DLESE OAI software is released under the <a href="http://www.dlese.org/oai/LICENSE.txt">GPL open source licence.</a> ! Individuals can download the software from the <a href="http://sourceforge.net/project/showfiles.php?group_id=23991">DLESE ! SourceForge</a> portal. Two zipped archives are made available for download: ! one contains a binary Java WAR file that can be deployed directly into a servlet ! container such as Tomcat for rapid deployment. The other contains a source code ! distribution that can be built and deployed using Ant.</p> <p>The software is deployed in three steps:</p> <ol> <li>The binary and source distributions are built with ant using the 'dist' ! target (see <a href="../../dds-project/docs/software-development-process.html">development ! process documentation</a> for details).</li> ! <li>The source and binary distributions are uploaded to the <a href="http://sourceforge.net/project/showfiles.php?group_id=23991">DLESE ! SourceForge</a> portal.</li> ! <li>Instructions and change notes are uploaded to the <a href="http://sourceforge.net/project/showfiles.php?group_id=23991">DLESE ! SourceForge</a> portal, and updated on the metadata web page as necessary.<br> </li> </ol> <h2> Testing and maintenance procedures </h2> ! See the <a href="../../dds-project/docs/software-development-process.html#testing">development ! process documentation section on testing</a>. <h2> Links to additional documentation </h2> --- 72,91 ---- communities as an out-of-the-box OAI solution. The DLESE OAI software is released under the <a href="http://www.dlese.org/oai/LICENSE.txt">GPL open source licence.</a> ! Two zipped archives are made available for download: ! one contains a binary Java WAR file that can be deployed directly into a servlet ! container such as Tomcat for rapid deployment. The other contains a source code ! distribution that can be built and deployed using Ant.</p> <p>The software is deployed in three steps:</p> <ol> <li>The binary and source distributions are built with ant using the 'dist' ! target (see development ! process documentation for details).</li> ! <li>The source and binary distributions are uploaded to the download server. </li> ! <li>Instructions and change notes are uploaded server, and updated on the metadata web page as necessary.<br> </li> </ol> <h2> Testing and maintenance procedures </h2> ! See the development ! process documentation section on testing. <h2> Links to additional documentation </h2> *************** *** 104,109 **** web site.</a></li> </ul> ! <p> <i>Contact: <a href="mailto:su...@dl...">su...@dl...</a></i><br> ! <i>Last updated: Oct 12, 2006</i><br> <i>Author: John Weatherley</i><br> </p> --- 100,105 ---- web site.</a></li> </ul> ! <p> <br> ! <i>Last updated: May, 2007 </i><br> <i>Author: John Weatherley</i><br> </p> |
|
From: John W. <jwe...@us...> - 2007-03-20 21:47:45
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv24469/web/docs Modified Files: CHANGES.txt product_release_config.xml Log Message: updated docs for release v3.0.10 Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.38 retrieving revision 1.39 diff -C2 -r1.38 -r1.39 *** CHANGES.txt 19 Mar 2007 18:12:04 -0000 1.38 --- CHANGES.txt 20 Mar 2007 21:47:38 -0000 1.39 *************** *** 6,10 **** ! v3.0.10 -Files are now explicitly read into the index using UTF-8 encoding instead of the --- 6,10 ---- ! v3.0.10 (Released March 20, 2007) -Files are now explicitly read into the index using UTF-8 encoding instead of the Index: product_release_config.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/product_release_config.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -r1.8 -r1.9 *** product_release_config.xml 23 Feb 2007 23:39:53 -0000 1.8 --- product_release_config.xml 20 Mar 2007 21:47:38 -0000 1.9 *************** *** 37,40 **** --- 37,59 ---- ]]> </description> + <release version="3.0.10"> + <notes> + <![CDATA[ + See: + <a href="/downloads/joai/v3.0.10/CHANGES.txt">changes in this version</a>, + <a href="/downloads/joai/v3.0.10/INSTALL.txt">installation instructions</a>, + <a href="/downloads/joai/v3.0.10/BUILD_INSTRUCTIONS.txt">building from source</a>, + <a href="/downloads/joai/v3.0.10/LICENSE.txt">software license</a>. + ]]> + </notes> + <link> + <name>Download binary application</name> + <url>/jsp/download/download.jsp?package=jOAI+3.0.10+Binary&url=/downloads/joai/v3.0.10/joai_v3.0.10.zip</url> + </link> + <link> + <name>Download source code</name> + <url>/jsp/download/download.jsp?package=jOAI+3.0.10+Source&url=/downloads/joai/v3.0.10/joai_v3.0.10_source.zip</url> + </link> + </release> <release version="3.0.9"> <notes> |
|
From: John W. <jwe...@us...> - 2007-03-19 19:01:27
|
Update of /cvsroot/dlese/oai-project/web In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv31497/web Added Files: browser.js Log Message: -Select lists are disabled for IE 6 and lower. IE 7 now properly supports z-index with select lists --- NEW FILE --- // Browser Detect v2.1.6 // documentation: http://www.dithered.com/javascript/browser_detect/index.html // license: http://creativecommons.org/licenses/by/1.0/ // code by Chris Nott (chris[at]dithered[dot]com) function BrowserDetect() { var ua = navigator.userAgent.toLowerCase(); // browser engine name this.isGecko = (ua.indexOf('gecko') != -1 && ua.indexOf('safari') == -1); this.isAppleWebKit = (ua.indexOf('applewebkit') != -1); // browser name this.isKonqueror = (ua.indexOf('konqueror') != -1); this.isSafari = (ua.indexOf('safari') != - 1); this.isOmniweb = (ua.indexOf('omniweb') != - 1); this.isOpera = (ua.indexOf('opera') != -1); this.isIcab = (ua.indexOf('icab') != -1); this.isAol = (ua.indexOf('aol') != -1); this.isIE = (ua.indexOf('msie') != -1 && !this.isOpera && (ua.indexOf('webtv') == -1) ); this.isMozilla = (this.isGecko && ua.indexOf('gecko/') + 14 == ua.length); this.isFirefox = (ua.indexOf('firefox/') != -1 || ua.indexOf('firebird/') != -1); this.isNS = ( (this.isGecko) ? (ua.indexOf('netscape') != -1) : ( (ua.indexOf('mozilla') != -1) && !this.isOpera && !this.isSafari && (ua.indexOf('spoofer') == -1) && (ua.indexOf('compatible') == -1) && (ua.indexOf('webtv') == -1) && (ua.indexOf('hotjava') == -1) ) ); // spoofing and compatible browsers this.isIECompatible = ( (ua.indexOf('msie') != -1) && !this.isIE); this.isNSCompatible = ( (ua.indexOf('mozilla') != -1) && !this.isNS && !this.isMozilla); // rendering engine versions this.geckoVersion = ( (this.isGecko) ? ua.substring( (ua.lastIndexOf('gecko/') + 6), (ua.lastIndexOf('gecko/') + 14) ) : -1 ); this.equivalentMozilla = ( (this.isGecko) ? parseFloat( ua.substring( ua.indexOf('rv:') + 3 ) ) : -1 ); this.appleWebKitVersion = ( (this.isAppleWebKit) ? parseFloat( ua.substring( ua.indexOf('applewebkit/') + 12) ) : -1 ); // browser version this.versionMinor = parseFloat(navigator.appVersion); // correct version number if (this.isGecko && !this.isMozilla) { this.versionMinor = parseFloat( ua.substring( ua.indexOf('/', ua.indexOf('gecko/') + 6) + 1 ) ); } else if (this.isMozilla) { this.versionMinor = parseFloat( ua.substring( ua.indexOf('rv:') + 3 ) ); } else if (this.isIE && this.versionMinor >= 4) { this.versionMinor = parseFloat( ua.substring( ua.indexOf('msie ') + 5 ) ); } else if (this.isKonqueror) { this.versionMinor = parseFloat( ua.substring( ua.indexOf('konqueror/') + 10 ) ); } else if (this.isSafari) { this.versionMinor = parseFloat( ua.substring( ua.lastIndexOf('safari/') + 7 ) ); } else if (this.isOmniweb) { this.versionMinor = parseFloat( ua.substring( ua.lastIndexOf('omniweb/') + 8 ) ); } else if (this.isOpera) { this.versionMinor = parseFloat( ua.substring( ua.indexOf('opera') + 6 ) ); } else if (this.isIcab) { this.versionMinor = parseFloat( ua.substring( ua.indexOf('icab') + 5 ) ); } this.versionMajor = parseInt(this.versionMinor); // dom support this.isDOM1 = (document.getElementById); this.isDOM2Event = (document.addEventListener && document.removeEventListener); // css compatibility mode this.mode = document.compatMode ? document.compatMode : 'BackCompat'; // platform this.isWin = (ua.indexOf('win') != -1); this.isWin32 = (this.isWin && ( ua.indexOf('95') != -1 || ua.indexOf('98') != -1 || ua.indexOf('nt') != -1 || ua.indexOf('win32') != -1 || ua.indexOf('32bit') != -1 || ua.indexOf('xp') != -1) ); this.isMac = (ua.indexOf('mac') != -1); this.isUnix = (ua.indexOf('unix') != -1 || ua.indexOf('sunos') != -1 || ua.indexOf('bsd') != -1 || ua.indexOf('x11') != -1) this.isLinux = (ua.indexOf('linux') != -1); // specific browser shortcuts this.isNS4x = (this.isNS && this.versionMajor == 4); this.isNS40x = (this.isNS4x && this.versionMinor < 4.5); this.isNS47x = (this.isNS4x && this.versionMinor >= 4.7); this.isNS4up = (this.isNS && this.versionMinor >= 4); this.isNS6x = (this.isNS && this.versionMajor == 6); this.isNS6up = (this.isNS && this.versionMajor >= 6); this.isNS7x = (this.isNS && this.versionMajor == 7); this.isNS7up = (this.isNS && this.versionMajor >= 7); this.isIE4x = (this.isIE && this.versionMajor == 4); this.isIE4up = (this.isIE && this.versionMajor >= 4); this.isIE5x = (this.isIE && this.versionMajor == 5); this.isIE55 = (this.isIE && this.versionMinor == 5.5); this.isIE5up = (this.isIE && this.versionMajor >= 5); this.isIE6x = (this.isIE && this.versionMajor == 6); this.isIE6up = (this.isIE && this.versionMajor >= 6); this.isIE6down = (this.isIE && this.versionMajor <= 6); this.isIE7x = (this.isIE && this.versionMajor == 7); this.isIE7up = (this.isIE && this.versionMajor >= 7); this.isIE4xMac = (this.isIE4x && this.isMac); } var browser = new BrowserDetect(); |
|
From: John W. <jwe...@us...> - 2007-03-19 18:12:14
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv13108/web/docs Modified Files: CHANGES.txt faq.jsp provider.jsp Log Message: -Added more documentation in the FAQ -upped the version Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.37 retrieving revision 1.38 diff -C2 -r1.37 -r1.38 *** CHANGES.txt 19 Mar 2007 17:06:27 -0000 1.37 --- CHANGES.txt 19 Mar 2007 18:12:04 -0000 1.38 *************** *** 10,19 **** -Files are now explicitly read into the index using UTF-8 encoding instead of the native system encoding type (rt ticket 6937). LC_CTYPE no longer needs to be set to UTF-8 in unix ! environments and encoding should now work properly on Windows. Expects the files reside ! in UTF-8 encoding. -Select lists in the UI are now disabled only for IE 6 and lower. IE 7 properly supports z-index layers with select lists. v3.0.9 (Released Feb 23, 2007) --- 10,21 ---- -Files are now explicitly read into the index using UTF-8 encoding instead of the native system encoding type (rt ticket 6937). LC_CTYPE no longer needs to be set to UTF-8 in unix ! environments and encoding should now work properly on Windows. Index Writers expect ! that the files reside in UTF-8 encoding. -Select lists in the UI are now disabled only for IE 6 and lower. IE 7 properly supports z-index layers with select lists. + -Added more documentation in the FAQ + v3.0.9 (Released Feb 23, 2007) Index: faq.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/faq.jsp,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** faq.jsp 17 Jan 2007 19:47:05 -0000 1.2 --- faq.jsp 19 Mar 2007 18:12:04 -0000 1.3 *************** *** 36,41 **** <p> </p> <h3><a name="provider" id="provider"></a>Provider FAQ</h3> <p><strong>What is different between the 'Search' and 'Admin search' pages?</strong></p> ! <p>The <a href="<c:url value='/search.jsp'/>">Search</a> page provides search over the full text found in all files that can be disseminated in oai_dc format. This includes files that reside natively in oai_dc format as well as files that --- 36,43 ---- <p> </p> <h3><a name="provider" id="provider"></a>Provider FAQ</h3> + <p><strong>Can I create a custom search page for the items in the data provider?</strong></p> + <p>Yes. The <a href="<c:url value='/search.jsp'/>">Search</a> page can be customized and easily installed to another location or remote Web server as described in the <a href="<c:url value='/docs/odlsearch.do'/>">ODL Search Specification</a> page. </p> <p><strong>What is different between the 'Search' and 'Admin search' pages?</strong></p> ! <p> The <a href="<c:url value='/search.jsp'/>">Search</a> page is intended to be accessed by the general public. It provides search over the full text found in all files that can be disseminated in oai_dc format. This includes files that reside natively in oai_dc format as well as files that *************** *** 43,60 **** files in multiple formats</a>. In addition, only files that are enabled in the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> ! page are available for search. The Search page is meant to be the public front ! for the data provider and can customized and easily installed to another location ! or remote Web server as described in the <a href="<c:url value='/docs/odlsearch.do'/>">ODL ! Search Specification</a> page. </p> ! <p>The <a href="<c:url value='/admin/query.do'/>">Admin search</a> page provides search over the full text found in all XML files that are configured in the data provider. Files are searchable and viewable even when public access to them has been disabled in the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> page. Admin search also provides options to search by ! set, available format, and record attribute (not deleted, deleted, etc.). The ! Admin search page resides in the administration portion of the software and ! its access can therefore be restricted to trusted users as described in the ! <a href="<c:url value='/docs/configuring_joai.jsp'/>">Configuring jOAI</a> page. ! </p> <p><strong>If my records reside in a database, can I use jOAI to implement an OAI data provider for my repository?</strong></p> <p>The jOAI data provider allows XML files from a file system to be exposed as items in an OAI data repository. To expose records that reside in a database, write a routine to export the records to XML files at regular intervals such as once a day or once a week, depending on how often the records change. Then <a href="<c:url value='/docs/provider.jsp#provsetup'/>">setup the data provider</a> to monitor the directory or directories where the files are exported to. See also <a href="<c:url value='/docs/provider.jsp#directories'/>">preparing files for serving</a>.</p> --- 45,55 ---- files in multiple formats</a>. In addition, only files that are enabled in the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> ! page are available for search. </p> ! <p>The <a href="<c:url value='/admin/query.do'/>">Admin search</a> page resides in the administration portion of the software and its access is intended to be restricted to trusted users as described in the <a href="<c:url value='/docs/configuring_joai.jsp'/>">Configuring jOAI</a> page. It provides search over the full text found in all XML files that are configured in the data provider. Files are searchable and viewable even when public access to them has been disabled in the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> page. Admin search also provides options to search by ! set, available format, and record attribute (not deleted, deleted, etc.).</p> <p><strong>If my records reside in a database, can I use jOAI to implement an OAI data provider for my repository?</strong></p> <p>The jOAI data provider allows XML files from a file system to be exposed as items in an OAI data repository. To expose records that reside in a database, write a routine to export the records to XML files at regular intervals such as once a day or once a week, depending on how often the records change. Then <a href="<c:url value='/docs/provider.jsp#provsetup'/>">setup the data provider</a> to monitor the directory or directories where the files are exported to. See also <a href="<c:url value='/docs/provider.jsp#directories'/>">preparing files for serving</a>.</p> *************** *** 166,169 **** --- 161,166 ---- <hr> <h3><a name="general" id="general"></a>General FAQ</h3> + <p><strong>Is it possible to customize the CSS, HTML or other features of the jOAI user interface?</strong></p> + <p>Yes. jOAI is rendered using CSS, HTML (which is generated by JSP), and JavaScript. Simply modify the .css, .jsp or .js files as desired to change the look-and-feel of the application. Tip: The struts-config.xml file found in WEB-INF describes what .jsp files are used to render certain portions of the application. The file head.jsp defines what items appear in the jOAI menus.</p> <p><strong>Can jOAI be configured to run through an Apache web server (httpd)?</strong></p> <p>Yes. Running jOAI through an <a href="http://httpd.apache.org/">Apache web *************** *** 193,196 **** --- 190,214 ---- <p>See the <a href="http://httpd.apache.org/docs/">Apache documentation</a> for a list of available features and configuration information.</p> + <p><strong>Can jOAI be integrated into an existing Web application? </strong></p> + <p>Yes. It is recommended that jOAI be run as a stand-alone Web application, however it is possible to integrate it into an existing Web application. Either the data provider, the harvester or both can be configured. Here is a general outline of how this may be done:</p> + <blockquote> + <p>1. Copy the configuration from web.xml:</p> + <ul> + <li>All <servlet> elements OAIProviderServlet, OAIHarvesterServlet and action.</li> + <li>All <context-param> elements</li> + <li>All <filter> and <filter-mapping> elements</li> + <li>All <servlet-mapping> elements</li> + <li>All <taglib> elements</li> + <li>Optionally, copy over the <welcome-file-list> and <error-page> elements</li> + </ul> + <p>2. Copy over files struts-config.xml, users.xml, validation.xml, validator-rules.xml from /WEB-INF to your application.</p> + <p>3. Copy over all JAR files from /WEB-INF/libs (some may not be required)</p> + <p>4. Copy over directories /WEB-INF/classes, /WEB-INF/tlds, /WEB-INF/xsl_files and /WEB-INF/conf. Optionally /WEB-INF/error_pages (if configured in web.xml).</p> + <p>5. Copy over all .jsp, .js and .css files from the root and the /oai_requests, /admin, /docs (optional), /images directories.</p> + <ul> + <li>Optionally edit, add and remove jsp and css files as needed. The OAI protocol is handled by the pages found in /oai_requests. Administration is handled by the pages found in /admin. The WEB-INF/struts-config.xml file is used to configure URL paths to the JSP pages that handle them, via the Action.</li> + </ul> + </blockquote> + <p> </p> <p> </p> <p><a href="faq.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> Index: provider.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/provider.jsp,v retrieving revision 1.28 retrieving revision 1.29 diff -C2 -r1.28 -r1.29 *** provider.jsp 31 Jan 2007 22:22:28 -0000 1.28 --- provider.jsp 19 Mar 2007 18:12:04 -0000 1.29 *************** *** 154,158 **** <li>Identifiers must be unique across all files configured in the data provider. It is an error to have two or more files, regardless of format, with the same identifier.</li> <li>For network efficiency, the file modification date should change only when the content of the file is modified. Changing the modification date initiates a transfer of the record from the data provider to the harvester.</li> ! <li>To comply with the <a href="http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse">XML response format</a> required by the OAI protocol, encoding of the XML must use the UTF-8 representation of Unicode and character references, rather than entity references, must be used. </li> </ul> <p><a href="provider.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> --- 154,158 ---- <li>Identifiers must be unique across all files configured in the data provider. It is an error to have two or more files, regardless of format, with the same identifier.</li> <li>For network efficiency, the file modification date should change only when the content of the file is modified. Changing the modification date initiates a transfer of the record from the data provider to the harvester.</li> ! <li>The XML files must be encoded using the UTF-8 representation of Unicode. Character references, rather than entity references, must used. See the <a href="http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse">XML response format</a> specification for the OAI protocol.</li> </ul> <p><a href="provider.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> |
|
From: John W. <jwe...@us...> - 2007-03-19 18:12:14
|
Update of /cvsroot/dlese/oai-project In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv13108 Modified Files: build.xml Log Message: -Added more documentation in the FAQ -upped the version Index: build.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/build.xml,v retrieving revision 1.69 retrieving revision 1.70 diff -C2 -r1.69 -r1.70 *** build.xml 20 Jan 2007 00:20:51 -0000 1.69 --- build.xml 19 Mar 2007 18:12:04 -0000 1.70 *************** *** 96,100 **** <property name="app.name" value="oai"/> ! <property name="app.version" value="3.0.9"/> <property name="oai.context.name" value="oai"/> <property name="deploy.context.name" value="${oai.context.name}"/> --- 96,100 ---- <property name="app.name" value="oai"/> ! <property name="app.version" value="3.0.10"/> <property name="oai.context.name" value="oai"/> <property name="deploy.context.name" value="${oai.context.name}"/> |
|
From: John W. <jwe...@us...> - 2007-03-19 18:12:12
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv22027/web/docs Modified Files: CHANGES.txt Log Message: -Select lists are disabled for IE 6 and lower. IE 7 now properly supports z-index with select lists -Comments about reding files for the index properly as utf-8 Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.36 retrieving revision 1.37 diff -C2 -r1.36 -r1.37 *** CHANGES.txt 23 Feb 2007 23:18:56 -0000 1.36 --- CHANGES.txt 19 Mar 2007 17:06:27 -0000 1.37 *************** *** 6,9 **** --- 6,20 ---- + v3.0.10 + + -Files are now explicitly read into the index using UTF-8 encoding instead of the + native system encoding type (rt ticket 6937). LC_CTYPE no longer needs to be set to UTF-8 in unix + environments and encoding should now work properly on Windows. Expects the files reside + in UTF-8 encoding. + + -Select lists in the UI are now disabled only for IE 6 and lower. IE 7 + properly supports z-index layers with select lists. + + v3.0.9 (Released Feb 23, 2007) |
|
From: John W. <jwe...@us...> - 2007-03-19 18:12:12
|
Update of /cvsroot/dlese/oai-project/web In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv22027/web Modified Files: head.jsp menu.js Log Message: -Select lists are disabled for IE 6 and lower. IE 7 now properly supports z-index with select lists -Comments about reding files for the index properly as utf-8 Index: head.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/head.jsp,v retrieving revision 1.25 retrieving revision 1.26 diff -C2 -r1.25 -r1.26 *** head.jsp 16 Jan 2007 03:15:39 -0000 1.25 --- head.jsp 19 Mar 2007 17:06:27 -0000 1.26 *************** *** 1,56 **** ! <%@ include file="TagLibIncludes.jsp" %> ! <script language="JavaScript"> ! <c:set var="menNum" value="0"/> ! var Menu1 = new Array () ! var subMenu1 = new Array () ! ! Menu1[${menNum}] = new Array("Overview", '<c:url value="/"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! <c:set var="menNum" value="${menNum + 1}"/> ! ! Menu1[${menNum}] = new Array ("Search", '<c:url value="/search.jsp"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! <c:set var="menNum" value="${menNum + 1}"/> ! ! Menu1[${menNum}] = new Array ("Explore", '<c:url value="/oaisearch.do"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! <c:set var="menNum" value="${menNum + 1}"/> ! ! <c:if test="${initParam.hideAdminMenus != 'true'}"> ! Menu1[${menNum}] = new Array("Provider", '<c:url value="/admin/provider_status_setup.jsp"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! subMenu1[${menNum}][0] = new Array ("Setup and Status", '<c:url value="/admin/provider_status_setup.jsp"/>',"_top") ! subMenu1[${menNum}][1] = new Array ("Repository Information and Administration", '<c:url value="/admin/data-provider-info.do"/>',"_top") ! subMenu1[${menNum}][2] = new Array ("Metadata Files Configuration", '<c:url value="/admin/data-provider.do"/>',"_top") ! subMenu1[${menNum}][3] = new Array ("Sets Configuration", '<c:url value="/admin/data-provider/sets.do"/>',"_top") ! subMenu1[${menNum}][4] = new Array ("Admin search", '<c:url value="/admin/query.do"/>',"_top") ! //subMenu1[${menNum}][5] = new Array ("ODL Search Explorer", '<c:url value="/oaisearch.do?show=odl"/>',"_top") ! //subMenu1[${menNum}][6] = new Array ("ODL Search Client", '<c:url value="/odl_search_client.jsp"/>',"_top") ! <c:set var="menNum" value="${menNum + 1}"/> ! ! Menu1[${menNum}] = new Array("Harvester", '<c:url value="/admin/harvester.do"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! subMenu1[${menNum}][0] = new Array ("Setup and Status", '<c:url value="/admin/harvester.do"/>',"_top") ! subMenu1[${menNum}][1] = new Array ("Harvest History and Progress", '<c:url value="/admin/harvestreport.do"/>?q=doctype:0harvestlog+AND+!repositoryname:%22One+time+harvest%22&s=0&report=Harvest+History+and+Progress', "_top") ! <c:set var="menNum" value="${menNum + 1}"/> ! </c:if> ! ! Menu1[${menNum}] = new Array("Documentation", '<c:url value="/docs/"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! subMenu1[${menNum}][0] = new Array ("Provider Documentation", '<c:url value="/docs/provider.jsp"/>',"_top") ! subMenu1[${menNum}][1] = new Array ("Harvester Documentation", '<c:url value="/docs/harvester.jsp"/>',"_top") ! subMenu1[${menNum}][2] = new Array ("Frequently Asked Questions (FAQ)", '<c:url value="/docs/faq.jsp"/>',"_top") ! subMenu1[${menNum}][3] = new Array ("ODL Search Specification", '<c:url value="/docs/odlsearch.do"/>',"_top") ! subMenu1[${menNum}][4] = new Array ("Installing jOAI", '<c:url value="/docs/INSTALL.txt"/>',"_top") ! subMenu1[${menNum}][5] = new Array ("Configuring jOAI", '<c:url value="/docs/configuring_joai.jsp"/>',"_top") ! subMenu1[${menNum}][6] = new Array ("About jOAI", '<c:url value="/docs/about.jsp"/>',"_top") ! <c:set var="menNum" value="${menNum + 1}"/> ! indicator = "<img src='${pageContext.request.contextPath}/images/tridown.gif' border='0'>" // Symbol to show if a sub menu is present (subIndicate must be to set to 1) ! // Use standard HTML <img> tag. You can use a character instead of an image. ! // e.g. indicator = ">" ! </script> ! <script type="text/javascript" src='${pageContext.request.contextPath}/menu.js'></script> ! <script type="text/javascript" src='${pageContext.request.contextPath}/oai_script.js'></script> ! ! <link rel="stylesheet" type="text/css" href='${pageContext.request.contextPath}/oai_styles.css'> ! --- 1,57 ---- ! <%@ include file="TagLibIncludes.jsp" %> ! <script language="JavaScript"> ! <c:set var="menNum" value="0"/> ! var Menu1 = new Array () ! var subMenu1 = new Array () ! ! Menu1[${menNum}] = new Array("Overview", '<c:url value="/"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! <c:set var="menNum" value="${menNum + 1}"/> ! ! Menu1[${menNum}] = new Array ("Search", '<c:url value="/search.jsp"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! <c:set var="menNum" value="${menNum + 1}"/> ! ! Menu1[${menNum}] = new Array ("Explore", '<c:url value="/oaisearch.do"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! <c:set var="menNum" value="${menNum + 1}"/> ! ! <c:if test="${initParam.hideAdminMenus != 'true'}"> ! Menu1[${menNum}] = new Array("Provider", '<c:url value="/admin/provider_status_setup.jsp"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! subMenu1[${menNum}][0] = new Array ("Setup and Status", '<c:url value="/admin/provider_status_setup.jsp"/>',"_top") ! subMenu1[${menNum}][1] = new Array ("Repository Information and Administration", '<c:url value="/admin/data-provider-info.do"/>',"_top") ! subMenu1[${menNum}][2] = new Array ("Metadata Files Configuration", '<c:url value="/admin/data-provider.do"/>',"_top") ! subMenu1[${menNum}][3] = new Array ("Sets Configuration", '<c:url value="/admin/data-provider/sets.do"/>',"_top") ! subMenu1[${menNum}][4] = new Array ("Admin search", '<c:url value="/admin/query.do"/>',"_top") ! //subMenu1[${menNum}][5] = new Array ("ODL Search Explorer", '<c:url value="/oaisearch.do?show=odl"/>',"_top") ! //subMenu1[${menNum}][6] = new Array ("ODL Search Client", '<c:url value="/odl_search_client.jsp"/>',"_top") ! <c:set var="menNum" value="${menNum + 1}"/> ! ! Menu1[${menNum}] = new Array("Harvester", '<c:url value="/admin/harvester.do"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! subMenu1[${menNum}][0] = new Array ("Setup and Status", '<c:url value="/admin/harvester.do"/>',"_top") ! subMenu1[${menNum}][1] = new Array ("Harvest History and Progress", '<c:url value="/admin/harvestreport.do"/>?q=doctype:0harvestlog+AND+!repositoryname:%22One+time+harvest%22&s=0&report=Harvest+History+and+Progress', "_top") ! <c:set var="menNum" value="${menNum + 1}"/> ! </c:if> ! ! Menu1[${menNum}] = new Array("Documentation", '<c:url value="/docs/"/>',"_top", "left") ! subMenu1[${menNum}] = new Array() ! subMenu1[${menNum}][0] = new Array ("Provider Documentation", '<c:url value="/docs/provider.jsp"/>',"_top") ! subMenu1[${menNum}][1] = new Array ("Harvester Documentation", '<c:url value="/docs/harvester.jsp"/>',"_top") ! subMenu1[${menNum}][2] = new Array ("Frequently Asked Questions (FAQ)", '<c:url value="/docs/faq.jsp"/>',"_top") ! subMenu1[${menNum}][3] = new Array ("ODL Search Specification", '<c:url value="/docs/odlsearch.do"/>',"_top") ! subMenu1[${menNum}][4] = new Array ("Installing jOAI", '<c:url value="/docs/INSTALL.txt"/>',"_top") ! subMenu1[${menNum}][5] = new Array ("Configuring jOAI", '<c:url value="/docs/configuring_joai.jsp"/>',"_top") ! subMenu1[${menNum}][6] = new Array ("About jOAI", '<c:url value="/docs/about.jsp"/>',"_top") ! <c:set var="menNum" value="${menNum + 1}"/> ! indicator = "<img src='${pageContext.request.contextPath}/images/tridown.gif' border='0'>" // Symbol to show if a sub menu is present (subIndicate must be to set to 1) ! // Use standard HTML <img> tag. You can use a character instead of an image. ! // e.g. indicator = ">" ! </script> ! <script type="text/javascript" src='${pageContext.request.contextPath}/browser.js'></script> ! <script type="text/javascript" src='${pageContext.request.contextPath}/menu.js'></script> ! <script type="text/javascript" src='${pageContext.request.contextPath}/oai_script.js'></script> ! ! <link rel="stylesheet" type="text/css" href='${pageContext.request.contextPath}/oai_styles.css'> ! Index: menu.js =================================================================== RCS file: /cvsroot/dlese/oai-project/web/menu.js,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -r1.4 -r1.5 *** menu.js 11 Apr 2006 19:35:05 -0000 1.4 --- menu.js 19 Mar 2007 17:06:27 -0000 1.5 *************** *** 1,346 **** ! ! ! /// FORMAT MENU /// ! menuStyle = "3d" // Menu Style (flat, 3d) ! cellPadding = "3" // Cell Padding ! cellBorder = 1 // Border width (for no border, enter 0) THIS VALUE APPLIES TO ALL MENUS ! verticalOffset = "0" // Vertical offset of Sub Menu. ! horizontalOffset = "0" // Horizontal offset of Sub Menu. ! subMenuDelay = 350 // Time sub menu stays visible for (in milliseconds). THIS VALUE APPLIES TO ALL MENUS ! subIndicate = 1 // Show if a sub menu is present (use 0 for "no") THIS VALUE APPLIES TO ALL MENUS ! ! // Main Menu Items ! menuWidth = "100" // Width of menu item. Use 0 for default ! borderColor = "#666666" // Border Colour (flat mode only) ! borderHighlight = "#666666" // Border Highlight Colour (3d mode only) ! borderShadow = "#666666" // Border Shadow Colour (3d mode only) ! menuBackground = "#A8B955" // Cell Background Colour ! menuHoverBackground = "#E7ECCF" // Cell Background Colour on mouse rollover ! fontFace = "arial" // Font Face ! fontColour = "#3f4c02" // Font Colour ! fontHoverColour = "#3f4c02" // Font Colour on mouse rollover ! fontSize = "10pt" // Font Size ! fontDecoration = "none" // Style of the link text (none, underline, overline, line-through) ! fontWeight = "normal" // Font Weight (normal, bold) ! ! // Sub Menu Items ! smenuWidth = "0" // Width of sub menu item. Use 0 for default ! sborderColor = "#666666" // Border Colour (flat mode only) ! sborderHighlight = "#666666" // Border Highlight Colour (3d mode only) ! sborderShadow = "#666666" // Border Shadow Colour (3d mode only) ! smenuBackground = "#BDCA80" // Cell Background Colour ! smenuHoverBackground = "#E7ECCF" // Cell Background Colour on mouse rolloverr ! sfontFace = "arial" // Font Face ! sfontColour = "#3f4c02" // Font Colour ! sfontHoverColour = "#3f4c02" // Font Colour on mouse rollover ! sfontSize = "10pt" // Font Size ! sfontDecoration = "none" // Style of the link text (none, underline, overline, line-through) ! sfontWeight = "normal" // Font Weight (normal, bold) ! ! quantity = 1 ! /// END FORMAT MENU //// ! ! /// DO NOT EDIT BELOW THIS LINE /// ! // Browser Sniffer ! var isIE = (document.getElementById && document.all)?true:false; ! var isNS4 = (document.layers)?true:false; ! var isNS6 = (document.getElementById && !document.all)?true:false; ! var timer; ! var obj = (isIE)?"document.all":"document.getElementById" ! // Menu Styles ! function createStyles(quant){ ! styleBorder=(menuStyle.split(",")[quant-1].toLowerCase() == "flat")?cellBorder:0 ! document.writeln ('<style>'); ! document.writeln ('.rcMenuStatic'+quant+' {font-family:'+fontFace.split(",")[quant-1]+';font-size:'+fontSize.split(",")[quant-1]+';color:'+fontColour.split(",")[quant-1]+';font-weight:'+fontWeight.split(",")[quant-1]+';background-color:'+menuBackground.split(",")[quant-1]+'; cursor:pointer; text-decoration:'+fontDecoration.split(",")[quant-1]+'}'); ! document.writeln ('.rcMenuHover'+quant+' {font-family:'+fontFace.split(",")[quant-1]+';font-size:'+fontSize.split(",")[quant-1]+';color:'+fontHoverColour.split(",")[quant-1]+';font-weight:'+fontWeight.split(",")[quant-1]+';background-color:'+menuHoverBackground.split(",")[quant-1]+'; cursor:pointer; text-decoration:'+fontDecoration.split(",")[quant-1]+'}'); ! document.writeln ('.rcSubMenuStatic'+quant+' {font-family:'+sfontFace.split(",")[quant-1]+';font-size:'+sfontSize.split(",")[quant-1]+';color:'+sfontColour.split(",")[quant-1]+';font-weight:'+sfontWeight.split(",")[quant-1]+';text-decoration:'+sfontDecoration.split(",")[quant-1]+';background-color:'+smenuBackground.split(",")[quant-1]+'; cursor:pointer}'); ! document.writeln ('.rcSubMenuHover'+quant+' {font-family:'+sfontFace.split(",")[quant-1]+';font-size:'+sfontSize.split(",")[quant-1]+';color:'+sfontHoverColour.split(",")[quant-1]+';font-weight:'+sfontWeight.split(",")[quant-1]+';text-decoration:'+sfontDecoration.split(",")[quant-1]+';background-color:'+smenuHoverBackground.split(",")[quant-1]+'; cursor:pointer}'); ! document.writeln ('</style>'); ! } ! // Build and show the main menu items ! function showMenus(quant,definedOrientation) ! { ! createStyles(quant); ! if(definedOrientation!=""){orientation=definedOrientation} ! document.writeln('<div onmouseenter="hideSelectLists(true);" onmouseleave="hideSelectLists(false); " >'); ! if (orientation.toLowerCase() == "vertical"){document.writeln ('<table border="0" cellpadding="0" cellspacing="'+styleBorder+'" bgColor="'+borderColor.split(",")[quant-1]+'">')} ! else{document.writeln ('<table border="0" cellpadding="0" cellspacing="'+styleBorder+'" bgColor="'+borderColor.split(",")[quant-1]+'"><tr>')} ! for (x=0; x<eval("Menu"+quant).length; x++) ! { ! if (orientation.toLowerCase()=="vertical") document.writeln('<tr>') ! document.writeln ('<td width="'+menuWidth+'" onclick="tdMouseClick(\''+quant+'mainLink'+x+'\')" onMouseOver="hoverMenu(); popDown(\''+quant+'\','+x+', \''+quant+'button'+x+'\',\''+orientation+'\'); " onMouseOut="clearMenu('+quant+','+x+'); " ') ! if (menuStyle.split(",")[quant-1].toLowerCase() == "3d"){document.writeln ('style="border-left:'+cellBorder+'px solid '+borderHighlight.split(",")[quant-1]+';border-top:'+cellBorder+'px solid '+borderHighlight.split(",")[quant-1]+';border-right:'+cellBorder+'px solid '+borderShadow.split(",")[quant-1]+';border-bottom:'+cellBorder+'px solid '+borderShadow.split(",")[quant-1]+';"');} ! document.writeln ('><div id="'+quant+'button'+x+'"><table border="0" cellpadding="'+cellPadding.split(",")[quant-1]+'" cellspacing="0" width="100%"><tr><td class="rcMenuStatic'+quant+'" id="'+quant+'cell'+x+'" nowrap>'); ! document.writeln ('<a style="text-decoration:none" id="'+quant+'mainLink'+x+'" href="'+eval("Menu"+quant)[x][1]+'" target="'+eval("Menu"+quant)[x][2]+'" class="rcMenuStatic'+quant+'">'+eval("Menu"+quant)[x][0]+'</a></td>'); ! if (subIndicate == 1&&eval("subMenu"+quant)[x].length>=1){ ! document.writeln('<td class="rcMenuStatic'+quant+'" id="'+quant+'cell'+x+'a" align="right">'); ! document.writeln ('<a style="text-decoration:none" id="'+quant+'mainLink'+x+'a" href="'+eval("Menu"+quant)[x][1]+'" target="'+eval("Menu"+quant)[x][2]+'" class="rcMenuStatic'+quant+'">'+indicator+'</a></td>');} ! document.writeln ('</tr></table></div></td>'); ! if (orientation.toLowerCase()=="vertical") document.writeln('</tr>') ! } ! if (orientation.toLowerCase() == "vertical"){document.writeln ('</table>');} ! else{document.writeln ('</tr></table>');} ! // Build the sub menu items ! for (x=0; x<eval("Menu"+quant).length; x++) ! { ! if (eval("subMenu"+quant)[x].length > 0) ! { ! document.writeln ('<div id="'+quant+'MENU'+x+'" style="visibility:hidden; position:absolute; z-index:2" >'); ! document.writeln ('<table width="'+smenuWidth.split(",")[quant-1]+'" border="0" cellpadding="'+cellPadding.split(",")[quant-1]+'" cellspacing="'+styleBorder+'" bgColor="'+sborderColor.split(",")[quant-1]+'">'); ! for (y=0; y<eval("subMenu"+quant)[x].length; y++) ! { ! document.writeln ('<tr>'); ! if (eval("subMenu"+quant)[x][y][1].indexOf("#") != -1) ! { ! document.writeln ('<td bgColor="'+eval("subMenu"+quant)[x][y][2]+'" id="'+quant+'subMenu'+x+y+'" onMouseOver="hoverMenu(); highlightMenu(\'sub\','+x+','+y+',\'\','+quant+'); " nowrap') ! if (menuStyle.split(",")[quant-1].toLowerCase() == "3d"){document.writeln ('style="border-left:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-top:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-right:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';border-bottom:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';"');} ! document.writeln ('><p style="font-family:'+sfontFace.split(",")[quant-1]+'; font-size:'+sfontSize.split(",")[quant-1]+'; color:'+eval("subMenu"+quant)[x][y][1]+'"id="'+quant+'subLink'+x+y+'">'+eval("subMenu"+quant)[x][y][0]+'</p></td></tr>'); ! } ! else ! { // this is the main menu items ! document.writeln ('<td id="'+quant+'subMenu'+x+y+'" class="rcSubMenuStatic'+quant+'" onMouseOver="hoverMenu(); highlightMenu(\'sub\','+x+','+y+',\'\','+quant+')" onMouseOut="clearMenu('+quant+','+x+'); " onclick="tdMouseClick(\''+quant+'subLink'+x+y+'\'); " nowrap') ! if (menuStyle.split(",")[quant-1].toLowerCase() == "3d"){document.writeln ('style="border-left:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-top:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-right:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';border-bottom:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';"');} ! document.writeln ('><a style="text-decoration:none" id="'+quant+'subLink'+x+y+'" href="'+eval("subMenu"+quant)[x][y][1]+'" target="'+eval("subMenu"+quant)[x][y][2]+'" class="rcSubMenuStatic'+quant+'">'+eval("subMenu"+quant)[x][y][0]+'</a></td></tr>'); ! } ! } ! document.writeln ('</table></div>'); ! } ! } ! document.writeln('</div>'); ! ! } ! ! function blah() ! { ! //setTimeout("hideSelectLists(false)",subMenuDelay-200); ! hideSelectLists(false); ! } ! // Change colour or menu and submenu items when the mouse hovers over. ! function highlightMenu(element,mainMenu,dropMenu,state,quant) ! { ! hoverMenu(); ! state=(state == "hover")?"rcMenuHover"+quant:"rcMenuStatic"+quant ! if (element == "sub") ! { ! for (x=0; x < eval("subMenu"+quant)[mainMenu].length; x++) ! { ! if (eval("subMenu"+quant)[mainMenu][x][1].indexOf("#") == -1){ ! eval(obj+'("'+quant+'subMenu'+mainMenu+x+'").className = "rcSubMenuStatic'+quant+'"') ! eval(obj+'("'+quant+'subLink'+mainMenu+x+'").className = "rcSubMenuStatic'+quant+'"') ! } ! } ! if (eval("subMenu"+quant)[mainMenu][dropMenu][1].indexOf("#") == -1) { ! eval(obj+'("'+quant+'subMenu'+mainMenu+dropMenu+'").className="rcSubMenuHover'+quant+'"') ! eval(obj+'("'+quant+'subLink'+mainMenu+dropMenu+'").className="rcSubMenuHover'+quant+'"') ! } ! } ! else ! { ! eval(obj+'("'+quant+'cell'+mainMenu+'").className = "'+state+'"') ! eval(obj+'("'+quant+'mainLink'+mainMenu+'").className = "'+state+'"') ! if (subIndicate == 1&&eval("subMenu"+quant)[mainMenu].length>=1) ! { ! eval(obj+'("'+quant+'cell'+mainMenu+'a").className = "'+state+'"') ! eval(obj+'("'+quant+'mainLink'+mainMenu+'a").className = "'+state+'"') ! } ! } ! } ! // Find positioning for sub menus ! function getOffset(obj, dim) ! { ! if(dim=="left") ! { ! oLeft = obj.offsetLeft; ! while(obj.offsetParent!=null) ! { ! oParent = obj.offsetParent ! oLeft += oParent.offsetLeft ! obj = oParent ! } ! return oLeft ! } ! else if(dim=="top") ! { ! oTop = obj.offsetTop; ! while(obj.offsetParent!=null) ! { ! oParent = obj.offsetParent ! oTop += oParent.offsetTop ! obj = oParent ! } ! return oTop ! } ! else if(dim=="width") ! { ! oWidth = obj.offsetWidth ! return oWidth ! } ! else if(dim=="height") ! { ! oHeight = obj.offsetHeight ! return oHeight ! } ! else ! { ! alert("Error: invalid offset dimension '" + dim + "' in getOffset()") ! return false; ! } ! } ! // Show sub menus ! function popDown(quant, param, id, orientation) ! { ! ! ! var cellBorderOffset = (isNS6)?cellBorder:eval(cellBorder*2) ! var browserAdjustment = (isNS6)?cellBorder:0 ! var menu; ! var button; ! ! ! if (id) ! { ! getOffset(eval(obj+'(id)'),'left'); ! getOffset(eval(obj+'(id)'),'top'); ! getOffset(eval(obj+'(id)'),'width'); ! getOffset(eval(obj+'(id)'),'height'); ! ! if (eval("Menu"+quant+"["+param+"][3]")=="right" && eval("subMenu"+quant+"["+param+"].length")>0) ! { ! oLeft=oLeft ! oLeft=oLeft+oWidth; ! getOffset(eval(obj+'("'+quant+'MENU'+param+'")'),'width'); ! oLeft=oLeft-oWidth ; ! alignAdjustment = cellBorder*2 + 1 ! } ! else ! { ! alignAdjustment = 0 ! oLeft=oLeft ! } ! } ! ! ! n = 0; ! while (n < eval("Menu"+quant).length) ! { ! menu = quant+"MENU"+n ! if (param == n) ! { ! theObj = eval(obj+'(menu)'); ! if (theObj) ! { ! theObj.style.visibility = "visible" ! if (orientation.toLowerCase()=="vertical"){ ! theObj.style.left=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oLeft+oWidth+cellBorder+parseInt(horizontalOffset.split(",")[quant-1]):oLeft+oWidth+cellBorderOffset+parseInt(horizontalOffset.split(",")[quant-1]); ! theObj.style.top=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oTop-cellBorder+parseInt(verticalOffset.split(",")[quant-1]):oTop+parseInt(verticalOffset.split(",")[quant-1])-browserAdjustment} ! else{ ! theObj.style.left=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oLeft-cellBorder+parseInt(horizontalOffset.split(",")[quant-1])+alignAdjustment:oLeft+parseInt(horizontalOffset.split(",")[quant-1])-browserAdjustment+alignAdjustment; ! theObj.style.top=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oTop+oHeight+cellBorder+parseInt(verticalOffset.split(",")[quant-1]):oTop+oHeight+cellBorderOffset+parseInt(verticalOffset.split(",")[quant-1]);} ! } ! ! highlightMenu('main',n,'','hover',quant) ! if (eval("subMenu"+quant)[param].length > 0) ! { ! for (x=0; x<eval("subMenu"+quant)[param].length; x++) ! { ! if(eval("subMenu"+quant)[param][x][1].indexOf("#") == -1){ ! eval (obj+'("'+quant+'subMenu'+param+x+'").className = "rcSubMenuStatic'+quant+'"') ! eval (obj+'("'+quant+'subLink'+param+x+'").className = "rcSubMenuStatic'+quant+'"') ! } ! } ! } ! } ! else ! { ! for (x=1; x<quantity+1; x++) ! { ! menu = x+"MENU"+n ! //alert(menu) ! if (eval(obj+'(menu)')) ! { ! eval(obj+'(menu).style.visibility = "hidden"'); ! } ! else ! { ! //hideSelectLists(false); ! } ! highlightMenu ('main',n,'','static',quant) ! } ! } ! ! n++ ! } ! ! ! } ! // Re-set timer for sub menus ! function hoverMenu() ! { ! if(timer){ ! clearTimeout(timer); ! } ! } ! // Set timer for sub menus ! function clearMenu(quant,menu) ! { ! setDelay = subMenuDelay; ! delay = (eval("subMenu"+quant)[menu].length > 0)?setDelay:1; ! timer = setTimeout("popDown("+quant+","+(eval("Menu"+quant).length + 1)+")",delay); ! } ! // when you click the box, perform the same function as if the user had clicked the hyperlink ! function tdMouseClick(theElement) ! { ! eval(obj+'(theElement).click()') ! } ! ! // IE select lists don't support z-index or zIndex, so we hide all of them: ! function hideSelectLists( hide ) { ! if ( isIE ) { ! for ( var i = 0; i < document.forms.length; i++ ) { ! for ( var j = 0; j < document.forms[i].elements.length; j++ ) { ! if ( document.forms[i].elements[j].type && ! ( document.forms[i].elements[j].type.indexOf( "select" ) == 0 ) ) { ! if ( hide ) ! document.forms[i].elements[j].style.visibility = "hidden"; ! else ! document.forms[i].elements[j].style.visibility = "visible"; ! } ! } ! } ! ! if ((! (document.getElementById('setsConfigPage'))) && (!(document.getElementById('addEditHPage'))) && (!(document.getElementById('odlDocsPage'))) ) ! // var sS = document.title; ! //if ((sS.indexOf("Edit Set") == -1) && (sS.indexOf("Add New Set") == -1)) ! { ! for ( var i = document.forms.length-1; i > -1 ; i-- ) { ! for ( var j = document.forms[i].elements.length -1; j > -1; j-- ) { ! if ( document.forms[i].elements[j].type && ! ( document.forms[i].elements[j].type.indexOf( "text" ) == 0 ) && ! document.forms[i].elements[j].style.visibility != 'hidden'){ ! if ( hide ) ! document.forms[i].elements[j].blur(); ! else ! { ! ! ! document.forms[i].elements[j].focus(); ! } ! } ! ! } ! } ! } ! } ! } ! ! // Trim white space around a string... ! function trim(s) ! { ! if(!s) ! return ""; ! while (s.substring(0,1) == ' ') ! s = s.substring(1, s.length); ! while (s.substring(s.length-1, s.length) == ' ') ! s = s.substring(0,s.length-1); ! return s; ! } --- 1,347 ---- ! ! ! /// FORMAT MENU /// ! menuStyle = "3d" // Menu Style (flat, 3d) ! cellPadding = "3" // Cell Padding ! cellBorder = 1 // Border width (for no border, enter 0) THIS VALUE APPLIES TO ALL MENUS ! verticalOffset = "0" // Vertical offset of Sub Menu. ! horizontalOffset = "0" // Horizontal offset of Sub Menu. ! subMenuDelay = 350 // Time sub menu stays visible for (in milliseconds). THIS VALUE APPLIES TO ALL MENUS ! subIndicate = 1 // Show if a sub menu is present (use 0 for "no") THIS VALUE APPLIES TO ALL MENUS ! ! // Main Menu Items ! menuWidth = "100" // Width of menu item. Use 0 for default ! borderColor = "#666666" // Border Colour (flat mode only) ! borderHighlight = "#666666" // Border Highlight Colour (3d mode only) ! borderShadow = "#666666" // Border Shadow Colour (3d mode only) ! menuBackground = "#A8B955" // Cell Background Colour ! menuHoverBackground = "#E7ECCF" // Cell Background Colour on mouse rollover ! fontFace = "arial" // Font Face ! fontColour = "#3f4c02" // Font Colour ! fontHoverColour = "#3f4c02" // Font Colour on mouse rollover ! fontSize = "10pt" // Font Size ! fontDecoration = "none" // Style of the link text (none, underline, overline, line-through) ! fontWeight = "normal" // Font Weight (normal, bold) ! ! // Sub Menu Items ! smenuWidth = "0" // Width of sub menu item. Use 0 for default ! sborderColor = "#666666" // Border Colour (flat mode only) ! sborderHighlight = "#666666" // Border Highlight Colour (3d mode only) ! sborderShadow = "#666666" // Border Shadow Colour (3d mode only) ! smenuBackground = "#BDCA80" // Cell Background Colour ! smenuHoverBackground = "#E7ECCF" // Cell Background Colour on mouse rolloverr ! sfontFace = "arial" // Font Face ! sfontColour = "#3f4c02" // Font Colour ! sfontHoverColour = "#3f4c02" // Font Colour on mouse rollover ! sfontSize = "10pt" // Font Size ! sfontDecoration = "none" // Style of the link text (none, underline, overline, line-through) ! sfontWeight = "normal" // Font Weight (normal, bold) ! ! quantity = 1 ! /// END FORMAT MENU //// ! ! /// DO NOT EDIT BELOW THIS LINE /// ! // Browser Sniffer (uses browser.js library) ! var isIE6down = browser.isIE6down; ! var isIE = (document.getElementById && document.all)?true:false; ! var isNS4 = (document.layers)?true:false; ! var isNS6 = (document.getElementById && !document.all)?true:false; ! var timer; ! var obj = (isIE)?"document.all":"document.getElementById" ! // Menu Styles ! function createStyles(quant){ ! styleBorder=(menuStyle.split(",")[quant-1].toLowerCase() == "flat")?cellBorder:0 ! document.writeln ('<style>'); ! document.writeln ('.rcMenuStatic'+quant+' {font-family:'+fontFace.split(",")[quant-1]+';font-size:'+fontSize.split(",")[quant-1]+';color:'+fontColour.split(",")[quant-1]+';font-weight:'+fontWeight.split(",")[quant-1]+';background-color:'+menuBackground.split(",")[quant-1]+'; cursor:pointer; text-decoration:'+fontDecoration.split(",")[quant-1]+'}'); ! document.writeln ('.rcMenuHover'+quant+' {font-family:'+fontFace.split(",")[quant-1]+';font-size:'+fontSize.split(",")[quant-1]+';color:'+fontHoverColour.split(",")[quant-1]+';font-weight:'+fontWeight.split(",")[quant-1]+';background-color:'+menuHoverBackground.split(",")[quant-1]+'; cursor:pointer; text-decoration:'+fontDecoration.split(",")[quant-1]+'}'); ! document.writeln ('.rcSubMenuStatic'+quant+' {font-family:'+sfontFace.split(",")[quant-1]+';font-size:'+sfontSize.split(",")[quant-1]+';color:'+sfontColour.split(",")[quant-1]+';font-weight:'+sfontWeight.split(",")[quant-1]+';text-decoration:'+sfontDecoration.split(",")[quant-1]+';background-color:'+smenuBackground.split(",")[quant-1]+'; cursor:pointer}'); ! document.writeln ('.rcSubMenuHover'+quant+' {font-family:'+sfontFace.split(",")[quant-1]+';font-size:'+sfontSize.split(",")[quant-1]+';color:'+sfontHoverColour.split(",")[quant-1]+';font-weight:'+sfontWeight.split(",")[quant-1]+';text-decoration:'+sfontDecoration.split(",")[quant-1]+';background-color:'+smenuHoverBackground.split(",")[quant-1]+'; cursor:pointer}'); ! document.writeln ('</style>'); ! } ! // Build and show the main menu items ! function showMenus(quant,definedOrientation) ! { ! createStyles(quant); ! if(definedOrientation!=""){orientation=definedOrientation} ! document.writeln('<div onmouseenter="hideSelectLists(true);" onmouseleave="hideSelectLists(false); " >'); ! if (orientation.toLowerCase() == "vertical"){document.writeln ('<table border="0" cellpadding="0" cellspacing="'+styleBorder+'" bgColor="'+borderColor.split(",")[quant-1]+'">')} ! else{document.writeln ('<table border="0" cellpadding="0" cellspacing="'+styleBorder+'" bgColor="'+borderColor.split(",")[quant-1]+'"><tr>')} ! for (x=0; x<eval("Menu"+quant).length; x++) ! { ! if (orientation.toLowerCase()=="vertical") document.writeln('<tr>') ! document.writeln ('<td width="'+menuWidth+'" onclick="tdMouseClick(\''+quant+'mainLink'+x+'\')" onMouseOver="hoverMenu(); popDown(\''+quant+'\','+x+', \''+quant+'button'+x+'\',\''+orientation+'\'); " onMouseOut="clearMenu('+quant+','+x+'); " ') ! if (menuStyle.split(",")[quant-1].toLowerCase() == "3d"){document.writeln ('style="border-left:'+cellBorder+'px solid '+borderHighlight.split(",")[quant-1]+';border-top:'+cellBorder+'px solid '+borderHighlight.split(",")[quant-1]+';border-right:'+cellBorder+'px solid '+borderShadow.split(",")[quant-1]+';border-bottom:'+cellBorder+'px solid '+borderShadow.split(",")[quant-1]+';"');} ! document.writeln ('><div id="'+quant+'button'+x+'"><table border="0" cellpadding="'+cellPadding.split(",")[quant-1]+'" cellspacing="0" width="100%"><tr><td class="rcMenuStatic'+quant+'" id="'+quant+'cell'+x+'" nowrap>'); ! document.writeln ('<a style="text-decoration:none" id="'+quant+'mainLink'+x+'" href="'+eval("Menu"+quant)[x][1]+'" target="'+eval("Menu"+quant)[x][2]+'" class="rcMenuStatic'+quant+'">'+eval("Menu"+quant)[x][0]+'</a></td>'); ! if (subIndicate == 1&&eval("subMenu"+quant)[x].length>=1){ ! document.writeln('<td class="rcMenuStatic'+quant+'" id="'+quant+'cell'+x+'a" align="right">'); ! document.writeln ('<a style="text-decoration:none" id="'+quant+'mainLink'+x+'a" href="'+eval("Menu"+quant)[x][1]+'" target="'+eval("Menu"+quant)[x][2]+'" class="rcMenuStatic'+quant+'">'+indicator+'</a></td>');} ! document.writeln ('</tr></table></div></td>'); ! if (orientation.toLowerCase()=="vertical") document.writeln('</tr>') ! } ! if (orientation.toLowerCase() == "vertical"){document.writeln ('</table>');} ! else{document.writeln ('</tr></table>');} ! // Build the sub menu items ! for (x=0; x<eval("Menu"+quant).length; x++) ! { ! if (eval("subMenu"+quant)[x].length > 0) ! { ! document.writeln ('<div id="'+quant+'MENU'+x+'" style="visibility:hidden; position:absolute; z-index:2" >'); ! document.writeln ('<table width="'+smenuWidth.split(",")[quant-1]+'" border="0" cellpadding="'+cellPadding.split(",")[quant-1]+'" cellspacing="'+styleBorder+'" bgColor="'+sborderColor.split(",")[quant-1]+'">'); ! for (y=0; y<eval("subMenu"+quant)[x].length; y++) ! { ! document.writeln ('<tr>'); ! if (eval("subMenu"+quant)[x][y][1].indexOf("#") != -1) ! { ! document.writeln ('<td bgColor="'+eval("subMenu"+quant)[x][y][2]+'" id="'+quant+'subMenu'+x+y+'" onMouseOver="hoverMenu(); highlightMenu(\'sub\','+x+','+y+',\'\','+quant+'); " nowrap') ! if (menuStyle.split(",")[quant-1].toLowerCase() == "3d"){document.writeln ('style="border-left:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-top:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-right:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';border-bottom:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';"');} ! document.writeln ('><p style="font-family:'+sfontFace.split(",")[quant-1]+'; font-size:'+sfontSize.split(",")[quant-1]+'; color:'+eval("subMenu"+quant)[x][y][1]+'"id="'+quant+'subLink'+x+y+'">'+eval("subMenu"+quant)[x][y][0]+'</p></td></tr>'); ! } ! else ! { // this is the main menu items ! document.writeln ('<td id="'+quant+'subMenu'+x+y+'" class="rcSubMenuStatic'+quant+'" onMouseOver="hoverMenu(); highlightMenu(\'sub\','+x+','+y+',\'\','+quant+')" onMouseOut="clearMenu('+quant+','+x+'); " onclick="tdMouseClick(\''+quant+'subLink'+x+y+'\'); " nowrap') ! if (menuStyle.split(",")[quant-1].toLowerCase() == "3d"){document.writeln ('style="border-left:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-top:'+cellBorder+'px solid '+sborderHighlight.split(",")[quant-1]+';border-right:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';border-bottom:'+cellBorder+'px solid '+sborderShadow.split(",")[quant-1]+';"');} ! document.writeln ('><a style="text-decoration:none" id="'+quant+'subLink'+x+y+'" href="'+eval("subMenu"+quant)[x][y][1]+'" target="'+eval("subMenu"+quant)[x][y][2]+'" class="rcSubMenuStatic'+quant+'">'+eval("subMenu"+quant)[x][y][0]+'</a></td></tr>'); ! } ! } ! document.writeln ('</table></div>'); ! } ! } ! document.writeln('</div>'); ! ! } ! ! function blah() ! { ! //setTimeout("hideSelectLists(false)",subMenuDelay-200); ! hideSelectLists(false); ! } ! // Change colour or menu and submenu items when the mouse hovers over. ! function highlightMenu(element,mainMenu,dropMenu,state,quant) ! { ! hoverMenu(); ! state=(state == "hover")?"rcMenuHover"+quant:"rcMenuStatic"+quant ! if (element == "sub") ! { ! for (x=0; x < eval("subMenu"+quant)[mainMenu].length; x++) ! { ! if (eval("subMenu"+quant)[mainMenu][x][1].indexOf("#") == -1){ ! eval(obj+'("'+quant+'subMenu'+mainMenu+x+'").className = "rcSubMenuStatic'+quant+'"') ! eval(obj+'("'+quant+'subLink'+mainMenu+x+'").className = "rcSubMenuStatic'+quant+'"') ! } ! } ! if (eval("subMenu"+quant)[mainMenu][dropMenu][1].indexOf("#") == -1) { ! eval(obj+'("'+quant+'subMenu'+mainMenu+dropMenu+'").className="rcSubMenuHover'+quant+'"') ! eval(obj+'("'+quant+'subLink'+mainMenu+dropMenu+'").className="rcSubMenuHover'+quant+'"') ! } ! } ! else ! { ! eval(obj+'("'+quant+'cell'+mainMenu+'").className = "'+state+'"') ! eval(obj+'("'+quant+'mainLink'+mainMenu+'").className = "'+state+'"') ! if (subIndicate == 1&&eval("subMenu"+quant)[mainMenu].length>=1) ! { ! eval(obj+'("'+quant+'cell'+mainMenu+'a").className = "'+state+'"') ! eval(obj+'("'+quant+'mainLink'+mainMenu+'a").className = "'+state+'"') ! } ! } ! } ! // Find positioning for sub menus ! function getOffset(obj, dim) ! { ! if(dim=="left") ! { ! oLeft = obj.offsetLeft; ! while(obj.offsetParent!=null) ! { ! oParent = obj.offsetParent ! oLeft += oParent.offsetLeft ! obj = oParent ! } ! return oLeft ! } ! else if(dim=="top") ! { ! oTop = obj.offsetTop; ! while(obj.offsetParent!=null) ! { ! oParent = obj.offsetParent ! oTop += oParent.offsetTop ! obj = oParent ! } ! return oTop ! } ! else if(dim=="width") ! { ! oWidth = obj.offsetWidth ! return oWidth ! } ! else if(dim=="height") ! { ! oHeight = obj.offsetHeight ! return oHeight ! } ! else ! { ! alert("Error: invalid offset dimension '" + dim + "' in getOffset()") ! return false; ! } ! } ! // Show sub menus ! function popDown(quant, param, id, orientation) ! { ! ! ! var cellBorderOffset = (isNS6)?cellBorder:eval(cellBorder*2) ! var browserAdjustment = (isNS6)?cellBorder:0 ! var menu; ! var button; ! ! ! if (id) ! { ! getOffset(eval(obj+'(id)'),'left'); ! getOffset(eval(obj+'(id)'),'top'); ! getOffset(eval(obj+'(id)'),'width'); ! getOffset(eval(obj+'(id)'),'height'); ! ! if (eval("Menu"+quant+"["+param+"][3]")=="right" && eval("subMenu"+quant+"["+param+"].length")>0) ! { ! oLeft=oLeft ! oLeft=oLeft+oWidth; ! getOffset(eval(obj+'("'+quant+'MENU'+param+'")'),'width'); ! oLeft=oLeft-oWidth ; ! alignAdjustment = cellBorder*2 + 1 ! } ! else ! { ! alignAdjustment = 0 ! oLeft=oLeft ! } ! } ! ! ! n = 0; ! while (n < eval("Menu"+quant).length) ! { ! menu = quant+"MENU"+n ! if (param == n) ! { ! theObj = eval(obj+'(menu)'); ! if (theObj) ! { ! theObj.style.visibility = "visible" ! if (orientation.toLowerCase()=="vertical"){ ! theObj.style.left=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oLeft+oWidth+cellBorder+parseInt(horizontalOffset.split(",")[quant-1]):oLeft+oWidth+cellBorderOffset+parseInt(horizontalOffset.split(",")[quant-1]); ! theObj.style.top=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oTop-cellBorder+parseInt(verticalOffset.split(",")[quant-1]):oTop+parseInt(verticalOffset.split(",")[quant-1])-browserAdjustment} ! else{ ! theObj.style.left=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oLeft-cellBorder+parseInt(horizontalOffset.split(",")[quant-1])+alignAdjustment:oLeft+parseInt(horizontalOffset.split(",")[quant-1])-browserAdjustment+alignAdjustment; ! theObj.style.top=(menuStyle.split(",")[quant-1].toLowerCase()=="flat")?oTop+oHeight+cellBorder+parseInt(verticalOffset.split(",")[quant-1]):oTop+oHeight+cellBorderOffset+parseInt(verticalOffset.split(",")[quant-1]);} ! } ! ! highlightMenu('main',n,'','hover',quant) ! if (eval("subMenu"+quant)[param].length > 0) ! { ! for (x=0; x<eval("subMenu"+quant)[param].length; x++) ! { ! if(eval("subMenu"+quant)[param][x][1].indexOf("#") == -1){ ! eval (obj+'("'+quant+'subMenu'+param+x+'").className = "rcSubMenuStatic'+quant+'"') ! eval (obj+'("'+quant+'subLink'+param+x+'").className = "rcSubMenuStatic'+quant+'"') ! } ! } ! } ! } ! else ! { ! for (x=1; x<quantity+1; x++) ! { ! menu = x+"MENU"+n ! //alert(menu) ! if (eval(obj+'(menu)')) ! { ! eval(obj+'(menu).style.visibility = "hidden"'); ! } ! else ! { ! //hideSelectLists(false); ! } ! highlightMenu ('main',n,'','static',quant) ! } ! } ! ! n++ ! } ! ! ! } ! // Re-set timer for sub menus ! function hoverMenu() ! { ! if(timer){ ! clearTimeout(timer); ! } ! } ! // Set timer for sub menus ! function clearMenu(quant,menu) ! { ! setDelay = subMenuDelay; ! delay = (eval("subMenu"+quant)[menu].length > 0)?setDelay:1; ! timer = setTimeout("popDown("+quant+","+(eval("Menu"+quant).length + 1)+")",delay); ! } ! // when you click the box, perform the same function as if the user had clicked the hyperlink ! function tdMouseClick(theElement) ! { ! eval(obj+'(theElement).click()') ! } ! ! // IE6 and earlier select lists don't support z-index or zIndex, so we hide all of them: ! function hideSelectLists( hide ) { ! if ( isIE6down ) { ! for ( var i = 0; i < document.forms.length; i++ ) { ! for ( var j = 0; j < document.forms[i].elements.length; j++ ) { ! if ( document.forms[i].elements[j].type && ! ( document.forms[i].elements[j].type.indexOf( "select" ) == 0 ) ) { ! if ( hide ) ! document.forms[i].elements[j].style.visibility = "hidden"; ! else ! document.forms[i].elements[j].style.visibility = "visible"; ! } ! } ! } ! ! if ((! (document.getElementById('setsConfigPage'))) && (!(document.getElementById('addEditHPage'))) && (!(document.getElementById('odlDocsPage'))) ) ! // var sS = document.title; ! //if ((sS.indexOf("Edit Set") == -1) && (sS.indexOf("Add New Set") == -1)) ! { ! for ( var i = document.forms.length-1; i > -1 ; i-- ) { ! for ( var j = document.forms[i].elements.length -1; j > -1; j-- ) { ! if ( document.forms[i].elements[j].type && ! ( document.forms[i].elements[j].type.indexOf( "text" ) == 0 ) && ! document.forms[i].elements[j].style.visibility != 'hidden'){ ! if ( hide ) ! document.forms[i].elements[j].blur(); ! else ! { ! ! ! document.forms[i].elements[j].focus(); ! } ! } ! ! } ! } ! } ! } ! } ! ! // Trim white space around a string... ! function trim(s) ! { ! if(!s) ! return ""; ! while (s.substring(0,1) == ' ') ! s = s.substring(1, s.length); ! while (s.substring(s.length-1, s.length) == ' ') ! s = s.substring(0,s.length-1); ! return s; ! } |
|
From: John W. <jwe...@us...> - 2007-02-23 23:39:56
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv504/web/docs Modified Files: product_release_config.xml Log Message: Index: product_release_config.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/product_release_config.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -r1.7 -r1.8 *** product_release_config.xml 19 Jan 2007 18:21:31 -0000 1.7 --- product_release_config.xml 23 Feb 2007 23:39:53 -0000 1.8 *************** *** 37,40 **** --- 37,59 ---- ]]> </description> + <release version="3.0.9"> + <notes> + <![CDATA[ + See: + <a href="/downloads/joai/v3.0.9/CHANGES.txt">changes in this version</a>, + <a href="/downloads/joai/v3.0.9/INSTALL.txt">installation instructions</a>, + <a href="/downloads/joai/v3.0.9/BUILD_INSTRUCTIONS.txt">building from source</a>, + <a href="/downloads/joai/v3.0.9/LICENSE.txt">software license</a>. + ]]> + </notes> + <link> + <name>Download binary application</name> + <url>/jsp/download/download.jsp?package=jOAI+3.0.9+Binary&url=/downloads/joai/v3.0.9/joai_v3.0.9.zip</url> + </link> + <link> + <name>Download source code</name> + <url>/jsp/download/download.jsp?package=jOAI+3.0.9+Source&url=/downloads/joai/v3.0.9/joai_v3.0.9_source.zip</url> + </link> + </release> <release version="3.0.8"> <notes> |
|
From: John W. <jwe...@us...> - 2007-02-23 23:18:58
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv25409/web/docs Modified Files: CHANGES.txt Log Message: added release date Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.35 retrieving revision 1.36 diff -C2 -r1.35 -r1.36 *** CHANGES.txt 23 Feb 2007 21:31:15 -0000 1.35 --- CHANGES.txt 23 Feb 2007 23:18:56 -0000 1.36 *************** *** 6,10 **** ! v3.0.9 -Added nsdl_dc to oai_dc xsl crosswalk --- 6,10 ---- ! v3.0.9 (Released Feb 23, 2007) -Added nsdl_dc to oai_dc xsl crosswalk |
|
From: John W. <jwe...@us...> - 2007-02-23 21:31:18
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv16711/web/docs Modified Files: CHANGES.txt Log Message: sp Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.34 retrieving revision 1.35 diff -C2 -r1.34 -r1.35 *** CHANGES.txt 23 Feb 2007 21:22:30 -0000 1.34 --- CHANGES.txt 23 Feb 2007 21:31:15 -0000 1.35 *************** *** 13,17 **** format converters, which can propagate as data corruption in the OAI ListRecords and GetRecord responses. Fixed by applying synchronization ! in the XSLConversionService to address this concurrency-related issue. --- 13,17 ---- format converters, which can propagate as data corruption in the OAI ListRecords and GetRecord responses. Fixed by applying synchronization ! in the XMLConversionService to address this concurrency-related issue. |
|
From: John W. <jwe...@us...> - 2007-02-23 21:22:33
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv14066/web/docs Modified Files: CHANGES.txt Log Message: -Fixed issue where corrupt XML data was being seen in the output from XSL format converters, which can propagate as data corruption in the OAI ListRecords and GetRecord responses. Fixed by applying synchronization in the XSLConversionService to address this concurrency-related issue. Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.33 retrieving revision 1.34 diff -C2 -r1.33 -r1.34 *** CHANGES.txt 20 Jan 2007 00:20:51 -0000 1.33 --- CHANGES.txt 23 Feb 2007 21:22:30 -0000 1.34 *************** *** 10,13 **** --- 10,18 ---- -Added nsdl_dc to oai_dc xsl crosswalk + -Fixed issue where corrupt XML data was being seen in the output from XSL + format converters, which can propagate as data corruption in the OAI + ListRecords and GetRecord responses. Fixed by applying synchronization + in the XSLConversionService to address this concurrency-related issue. + v3.0.8 (Released Jan 19, 2007) |
|
From: John W. <jwe...@us...> - 2007-01-31 22:40:37
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv6772/web/docs Modified Files: provider.jsp Log Message: added nsdl_dc to oai_dc converter in docs Index: provider.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/provider.jsp,v retrieving revision 1.27 retrieving revision 1.28 diff -C2 -r1.27 -r1.28 *** provider.jsp 16 Jan 2007 03:15:40 -0000 1.27 --- provider.jsp 31 Jan 2007 22:22:28 -0000 1.28 *************** *** 1,212 **** ! <%@ page contentType="text/html; charset=UTF-8" %> ! <%@ include file="../TagLibIncludes.jsp" %> ! <%@ include file="../baseUrl.jsp" %> ! <c:set var="rm" value="${applicationScope.repositoryManager}"/> ! ! <html> ! ! <head> ! <title>jOAI Provider Documentation</title> ! <c:import url="../head.jsp"/> ! <style type="text/css"> ! <!-- ! .code {font-family: "Courier New", Courier, mono} ! --> ! </style> ! </head> ! ! <body> ! <a name="top"></a><c:import url="../top.jsp?sec=doc"/> ! <!-- content begins--> ! <h1>Provider Documentation</h1> ! <p>This documentation includes the following sections: </p> ! <table border="0" align="left" cellpadding="0" cellspacing="0"> ! <tr> ! <td align="left"><a href="provider.jsp#overview">Overview</a></td> ! </tr> ! <tr> ! <td align="left"><a href="provider.jsp#provsetup">Provider setup </a></td> ! </tr> ! <tr> ! <td align="left"><a href="provider.jsp#directories">Preparing files for serving </a></td> ! </tr> ! <tr> ! <td align="left"><a href="provider.jsp#convertors">Providing files in multiple formats </a></td> ! </tr> ! </table> ! ! <p> </p> ! <p> </p> ! <p> </p> ! <p> </p> ! <h3><a name="overview"></a>Overview</h3> ! <p>The jOAI data provider allows XML files from a file system to be exposed as items in an OAI data repository and made available for harvesting by others using the OAI-PMH. After pointing the software to one or more file directories, the software monitors the XML files inside, adding, updating or deleting them from the OAI repository as files are added, updated or deleted from the directories. Remote harvesters that monitor the OAI data repository can effectively mirror the files or harvest them as needed. jOAI can provide any XML format as long as the XML in the file is well formed.</p> ! <p>The jOAI data provider implements protocol version 2.0. It uses resumption ! tokens for <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#FlowControl" ! >flow control</a> in the <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ListIdentifiers" >ListIdentifiers</a> ! and <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ListRecords">ListRecords</a> ! responses, supports selective harvesting by <a ! href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#SelectiveHarvestingandDatestamps">date</a> ! or <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#SelectiveHarvestingandSets">set</a>, ! provides gzip <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ResponseCompression">response ! compression</a> and other protocol features.</p> ! <p>See the <a href="<c:url value='/docs/faq.jsp#provider'/>">Provider FAQ</a> ! for additional information.</p> ! <hr> ! <a name="provsetup"></a> ! <h3>Provider setup</h3> ! <p>There are five steps necessary to make metadata files available through the jOAI data provider: </p> ! <p>1. Install the jOAI software on a system in a servlet container such as <a href="http://tomcat.apache.org/">Apache Tomcat</a>. </p> ! <p>See <a href="INSTALL.txt">INSTALL.txt</a> for installation instructions. If reading this page, most likely this step has been completed. </p> ! <p>2. Complete the <a href="<c:url value='/admin/data-provider-info.do'/>">Repository Information</a> by clicking 'Edit repository info' in the Repository Information and Administration page and then:</p> ! <ul> ! <li>Enter a repository name (<em>required</em>) </li> ! <li>Include an administrators e-mail address (<em>required</em>) </li> ! <li> Provide a namespace identifier (<em>optional but strongly recommended</em>) </li> ! <li>Provide a description (<em>optional</em>) </li> ! </ul> ! <p>The <strong>namespace-identifier</strong> is similar to an Internet domain name, for example "dlese.org" or "project.dlese.org." If specified, the namespace identifier is used to compose the OAI Identifier for items in the repository. See the ! <a href="http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm">OAI Identifier Format</a> guidelines ! for more information. </p> ! <p>Leave the <strong>description</strong> blank if not using. </p> ! <p>3. Complete the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> in the Metadata Files Configuration page by adding one or more metadata directories to the repository. For each directory: </p> ! <ul> ! <li>Enter an appropriate nickname for the directory of files (<em>required</em>) </li> ! <li>Provide the metadata format (metadataPrefix) of the files (<em>required</em>) </li> ! <li>Enter the complete directory path to the metadata files (<em>required</em>)</li> ! <li>Enter the metadata namespace and schema for the format (<em>optional but recommended</em>) </li> ! </ul> ! <p>The <strong>directory of files</strong> must contain XML files that conform to the rules described below under <a href="#directories">Preparing files for serving</a>.</p> ! <p>The <strong>metadata format</strong> may be any metadata (or data) format. ! In the OAI protocol, the format specifier is know as the <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#MetadataNamespaces">metadataPrefix</a>. ! The metadataPrefix may be any combination of <a href="http://www.ietf.org/rfc/rfc2396.txt">URI <i>unreserved</i> characters</a>, such as ! letters, numbers, underscores and dashes. ! <blockquote> ! <p> ! Examples: ! </p> ! ! <table border="0"> ! <tr> ! <td class="code">oai_dc</td> ! <td>- Dublin Core format</td> ! </tr> ! <tr> ! <td class="code">adn</td> ! <td>- ADN format</td> ! </tr> ! <tr> ! <td>dlese_anno</td> ! <td>- DLESE annotation format</td> ! </tr> ! <tr> ! <td>dlese_collect</td> ! <td>- DLESE collection format</td> ! </tr> ! <tr> ! <td>news_opps</td> ! <td>- DLESE news and opportunities format</td> ! </tr> ! </table> ! </blockquote> ! ! <p> In general, the <b>metadata namespace and schema</b> can be found near the top of an XML file for the given format. ! If the format is recognized by the software these fields will be filled in automatically. </p> ! <p>4. After completing step 3, the software automatically indexes the metadata files, which may take several minutes to complete. Once the files are indexed, the metadata is available for harvesting, for browsing using the OAI protocol via the <a href="<c:url value='/oaisearch.do'/>">Explorer</a> page and for textual searching using the <a href="/oai/search.jsp">Search</a> or <a href="<c:url value='/admin/query.do'/>">Admin search</a> pages. The <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> shows information about the status of the files and indexing process. If metadata files are added, modified or deleted at a later time, the software automatically detects these changes and adds, deletes or re-indexes them ! every ! <%@ include file="../updateFrequency.jsp" %>. ! The index can also be updated manually at any time from the <a href="<c:url value='/admin/data-provider.do#index'/>">Files index administration</a> area.</p> ! <p>5. Complete <a href="<c:url value='/admin/data-provider/sets.do'/>">Sets Configuration</a>. This step is <em>optional</em>. Define a new set and then: </p> ! <ul> ! <li>Enter a set name (<em>required </em>) </li> ! <li>Enter a setSpec (<em>required </em>) </li> ! <li>Provide a set description (<em>optional </em>) </li> ! <li>Add records to the newly created set by defining which records to include in the set (<em>required </em>) </li> ! </ul> ! <p>The <strong>set name </strong> is a descriptive name for a group of metadata files that are a subgroup of all metadata files in the repository, for example "DLESE Community Collection".</p> ! <p>The <strong>setSpec </strong> is a unique name or label that identifies the subgroup of metadata files; harvesters may use a setSpec to identify and get the correct set of metadata files from providers. A setSpec example is "dcc."</p> ! <p>Limit the number files in a set by specifying certain directories, metadata formats or search criteria. </p> ! <p>The optional <strong>description </strong> field contains information about the content, purpose, rights or history of the provider. Leave the description field blank if no information is available. </p> ! <p>After completing the steps above, metadata files are available for harvesting by others. </p> ! <p>This software supports the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), version 2.0. Detailed information about the protocol is outside the scope of this documentation. For background information on the OAI-PMH, please refer to the official <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm" >OAI-PMH documentation</a> and to additional information and tutorials available through the <a href="http://www.openarchives.org">Open Archives Initiative</a>. </p> ! <p><a href="provider.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="directories"></a>Preparing files for serving</h3> ! <p>jOAI monitors each directory of files that is configured in the system and automatically adds, updates or deletes items from the OAI repository as files are added, updated or deleted from the directories. ! <c:choose> ! <c:when test="${rm.updateFrequency > 0}"> ! After the initial configuration, the synchronization between the files and the OAI repository occurs automatically every ! <%@ include file="../updateFrequency.jsp" %> ! or may be <a href="<c:url value='/admin/data-provider.do#index'/>">synchronized manually</a> at any time. ! </c:when> ! </c:choose> ! ! ! ! </p> ! <p>To ensure proper operation, files must follow these conventions: </p> ! <ul> ! <li>Each file must be a well-formed XML instance document.</li> ! <li>Each file must contain a single record, which corresponds to a single item in the OAI repository.</li> ! <li>All files within a given directory must be of the same metadata (XML) format.</li> ! <li>Each file name must end with a .xml file extension. </li> ! <li>The file name up to the .xml file extension must indicate a <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#UniqueIdentifier" >unique identifier</a> for the record*. For example, if the file is named <span class="code">abc-123.xml</span>, the identifier for the record will be <span class="code">abc-123</span> (the identifier is used as the local identifier portion of the <a href="http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm">OAI Identifier Format</a> in the OAI protocol). Identifiers in jOAI are <em>not</em> case sensitive. *Note that for files in the <span class="code">adn</span>, <span class="code">dlese_anno</span>, <span class="code">dlese_collect</span> and <span class="code">news_opps</span> formats, the file name is not used and instead the identifier must be indicated in the proper location in the file's XML.</li> ! <li>Identifiers must be unique across all files configured in the data provider. It is an error to have two or more files, regardless of format, with the same identifier.</li> ! <li>For network efficiency, the file modification date should change only when the content of the file is modified. Changing the modification date initiates a transfer of the record from the data provider to the harvester.</li> ! <li>To comply with the <a href="http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse">XML response format</a> required by the OAI protocol, encoding of the XML must use the UTF-8 representation of Unicode and character references, rather than entity references, must be used. </li> ! </ul> ! <p><a href="provider.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="convertors"></a>Providing files in multiple formats </h3> ! <p>jOAI can disseminate any given metadata file in multiple formats. For example, a file that resides in the <span class="code">adn</span> format can also be disseminated to harvesters in the <span class="code">oai_dc</span> format. This is done using metadata format converters. Several metadata format converters come pre-configured in the software as detailed below. New converters can be configured and implemented using an XSL stylesheet or a custom Java class that converts metadata from its native XML format to another XML format. Once a format converter is configured, all files in the native format will be disseminated in either the native or converted format depending on which format is requested by the harvester. </p> ! <p>The software comes pre-configured with the following metadata format converters:</p> ! <table border="1" cellspacing="0" cellpadding="0"> ! <tr> ! <td><strong>Native XML format </strong></td> ! <td><strong>Converted XML format </strong></td> ! </tr> ! <tr> ! <td class="code">adn </td> ! <td><span class="code">oai_dc</span>, <span class="code">nsdl_dc</span>, <span class="code">briefmeta</span> </td> ! </tr> ! <tr> ! <td class="code">dlese_anno </td> ! <td class="code">oai_dc </td> ! </tr> ! <tr> ! <td class="code">dlese_collect </td> ! <td class="code">oai_dc </td> ! </tr> ! <tr> ! <td class="code">news_opps </td> ! <td class="code">oai_dc </td> ! </tr> ! </table> ! <p>To configure additional metadata format converters, do the following: </p> ! <p>1. Create or obtain an XSL stylesheet or Java class that performs the desired format conversion from one XML format to another. The converter takes XML in the native format as its input and must generate XML in the converted format as its output. For Java converters, the class must implement the <a href="<c:url value='/docs/javadoc/org/dlese/dpc/xml/XMLFormatConverter.html'/>" class="code">XMLFormatConverter</a> Interface. </p> ! <p>2. If using an XSL stylesheet to perform the conversion, place it in the "xsl_files" directory located in the "WEB-INF" directory of the OAI software context. If using a Java class to perform the conversion, place the class binary anywhere within the classpath of the servlet container. </p> ! <p>3. Edit the"web.xml" file located in the "WEB-INF" directory and add a context-param element to configure each format converter (see the existing ones for examples).When configuring an XSL converter, the param-name element must start with the string with "xslconverter," followed by additional descriptive text. When configuring a Java class converter, the param-name element must start with the string with "javaconverter," followed by additional descriptive text. Each param-name must be unique; otherwise it will not be recognized. ! <p>For the param-value field, supply a string of the form ! <p class="code">[convertername] | [from format] | [to format] ! <p>where convertername is either the name of an XSL file or a fully qualified Java class and the "to" and "from" formats are metadataPrefixes for the given formats. </p> ! <p>For example, an XSL stylesheet named myDCConverter.xsl that converts from ADN to Dublin Core, the param-value would be </p> ! <p>"<span class="code">myDCConverter.xsl|adn|oai_dc</span>" (quotes omitted). </p> ! <p>For a Java class converter by the full name org.institution.converter.MyDCConverter, the param-value would be </p> ! <p>"<span class="code">org.institution.converter.MyDCConverter|adn|oai_dc</span>" (quotes omitted).</p> ! <p>An example of a complete context-param configuration for a format converter looks like the following:</p> ! ! <pre class="code"> ! <context-param> ! <param-name>xslconverter - adn to oai_dc converter</param-name> ! <param-value>adn-v0.6.50-to-oai_dc.xsl|adn|oai_dc</param-value> ! </context-param> </pre> ! <p>4. After configuring the web.xml file and placing the converter in the appropriate location, start or restart the software. The software automatically recognizes the converter and adds the new format to its list of available formats and exposed in response to the OAI <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ListMetadataFormats" class="code">ListMetadataFormats</a> request. </p> ! <p>Tip: The format converter module caches the converted metadata to disk for ! increased performance. These converted files may be accessed locally. Accessed ! files are cached in the "WEB-INF/repository_data/converted_xml_cache" ! directory. </p> ! <p><a href="provider.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <c:import url="../bottom.jsp"/> ! </body> ! </html> ! --- 1,216 ---- ! <%@ page contentType="text/html; charset=UTF-8" %> ! <%@ include file="../TagLibIncludes.jsp" %> ! <%@ include file="../baseUrl.jsp" %> ! <c:set var="rm" value="${applicationScope.repositoryManager}"/> ! ! <html> ! ! <head> ! <title>jOAI Provider Documentation</title> ! <c:import url="../head.jsp"/> ! <style type="text/css"> ! <!-- ! .code {font-family: "Courier New", Courier, mono} ! --> ! </style> ! </head> ! ! <body> ! <a name="top"></a><c:import url="../top.jsp?sec=doc"/> ! <!-- content begins--> ! <h1>Provider Documentation</h1> ! <p>This documentation includes the following sections: </p> ! <table border="0" align="left" cellpadding="0" cellspacing="0"> ! <tr> ! <td align="left"><a href="provider.jsp#overview">Overview</a></td> ! </tr> ! <tr> ! <td align="left"><a href="provider.jsp#provsetup">Provider setup </a></td> ! </tr> ! <tr> ! <td align="left"><a href="provider.jsp#directories">Preparing files for serving </a></td> ! </tr> ! <tr> ! <td align="left"><a href="provider.jsp#convertors">Providing files in multiple formats </a></td> ! </tr> ! </table> ! ! <p> </p> ! <p> </p> ! <p> </p> ! <p> </p> ! <h3><a name="overview"></a>Overview</h3> ! <p>The jOAI data provider allows XML files from a file system to be exposed as items in an OAI data repository and made available for harvesting by others using the OAI-PMH. After pointing the software to one or more file directories, the software monitors the XML files inside, adding, updating or deleting them from the OAI repository as files are added, updated or deleted from the directories. Remote harvesters that monitor the OAI data repository can effectively mirror the files or harvest them as needed. jOAI can provide any XML format as long as the XML in the file is well formed.</p> ! <p>The jOAI data provider implements protocol version 2.0. It uses resumption ! tokens for <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#FlowControl" ! >flow control</a> in the <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ListIdentifiers" >ListIdentifiers</a> ! and <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ListRecords">ListRecords</a> ! responses, supports selective harvesting by <a ! href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#SelectiveHarvestingandDatestamps">date</a> ! or <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#SelectiveHarvestingandSets">set</a>, ! provides gzip <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ResponseCompression">response ! compression</a> and other protocol features.</p> ! <p>See the <a href="<c:url value='/docs/faq.jsp#provider'/>">Provider FAQ</a> ! for additional information.</p> ! <hr> ! <a name="provsetup"></a> ! <h3>Provider setup</h3> ! <p>There are five steps necessary to make metadata files available through the jOAI data provider: </p> ! <p>1. Install the jOAI software on a system in a servlet container such as <a href="http://tomcat.apache.org/">Apache Tomcat</a>. </p> ! <p>See <a href="INSTALL.txt">INSTALL.txt</a> for installation instructions. If reading this page, most likely this step has been completed. </p> ! <p>2. Complete the <a href="<c:url value='/admin/data-provider-info.do'/>">Repository Information</a> by clicking 'Edit repository info' in the Repository Information and Administration page and then:</p> ! <ul> ! <li>Enter a repository name (<em>required</em>) </li> ! <li>Include an administrators e-mail address (<em>required</em>) </li> ! <li> Provide a namespace identifier (<em>optional but strongly recommended</em>) </li> ! <li>Provide a description (<em>optional</em>) </li> ! </ul> ! <p>The <strong>namespace-identifier</strong> is similar to an Internet domain name, for example "dlese.org" or "project.dlese.org." If specified, the namespace identifier is used to compose the OAI Identifier for items in the repository. See the ! <a href="http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm">OAI Identifier Format</a> guidelines ! for more information. </p> ! <p>Leave the <strong>description</strong> blank if not using. </p> ! <p>3. Complete the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> in the Metadata Files Configuration page by adding one or more metadata directories to the repository. For each directory: </p> ! <ul> ! <li>Enter an appropriate nickname for the directory of files (<em>required</em>) </li> ! <li>Provide the metadata format (metadataPrefix) of the files (<em>required</em>) </li> ! <li>Enter the complete directory path to the metadata files (<em>required</em>)</li> ! <li>Enter the metadata namespace and schema for the format (<em>optional but recommended</em>) </li> ! </ul> ! <p>The <strong>directory of files</strong> must contain XML files that conform to the rules described below under <a href="#directories">Preparing files for serving</a>.</p> ! <p>The <strong>metadata format</strong> may be any metadata (or data) format. ! In the OAI protocol, the format specifier is know as the <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#MetadataNamespaces">metadataPrefix</a>. ! The metadataPrefix may be any combination of <a href="http://www.ietf.org/rfc/rfc2396.txt">URI <i>unreserved</i> characters</a>, such as ! letters, numbers, underscores and dashes. ! <blockquote> ! <p> ! Examples: ! </p> ! ! <table border="0"> ! <tr> ! <td class="code">oai_dc</td> ! <td>- Dublin Core format</td> ! </tr> ! <tr> ! <td class="code">adn</td> ! <td>- ADN format</td> ! </tr> ! <tr> ! <td>dlese_anno</td> ! <td>- DLESE annotation format</td> ! </tr> ! <tr> ! <td>dlese_collect</td> ! <td>- DLESE collection format</td> ! </tr> ! <tr> ! <td>news_opps</td> ! <td>- DLESE news and opportunities format</td> ! </tr> ! </table> ! </blockquote> ! ! <p> In general, the <b>metadata namespace and schema</b> can be found near the top of an XML file for the given format. ! If the format is recognized by the software these fields will be filled in automatically. </p> ! <p>4. After completing step 3, the software automatically indexes the metadata files, which may take several minutes to complete. Once the files are indexed, the metadata is available for harvesting, for browsing using the OAI protocol via the <a href="<c:url value='/oaisearch.do'/>">Explorer</a> page and for textual searching using the <a href="/oai/search.jsp">Search</a> or <a href="<c:url value='/admin/query.do'/>">Admin search</a> pages. The <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> shows information about the status of the files and indexing process. If metadata files are added, modified or deleted at a later time, the software automatically detects these changes and adds, deletes or re-indexes them ! every ! <%@ include file="../updateFrequency.jsp" %>. ! The index can also be updated manually at any time from the <a href="<c:url value='/admin/data-provider.do#index'/>">Files index administration</a> area.</p> ! <p>5. Complete <a href="<c:url value='/admin/data-provider/sets.do'/>">Sets Configuration</a>. This step is <em>optional</em>. Define a new set and then: </p> ! <ul> ! <li>Enter a set name (<em>required </em>) </li> ! <li>Enter a setSpec (<em>required </em>) </li> ! <li>Provide a set description (<em>optional </em>) </li> ! <li>Add records to the newly created set by defining which records to include in the set (<em>required </em>) </li> ! </ul> ! <p>The <strong>set name </strong> is a descriptive name for a group of metadata files that are a subgroup of all metadata files in the repository, for example "DLESE Community Collection".</p> ! <p>The <strong>setSpec </strong> is a unique name or label that identifies the subgroup of metadata files; harvesters may use a setSpec to identify and get the correct set of metadata files from providers. A setSpec example is "dcc."</p> ! <p>Limit the number files in a set by specifying certain directories, metadata formats or search criteria. </p> ! <p>The optional <strong>description </strong> field contains information about the content, purpose, rights or history of the provider. Leave the description field blank if no information is available. </p> ! <p>After completing the steps above, metadata files are available for harvesting by others. </p> ! <p>This software supports the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), version 2.0. Detailed information about the protocol is outside the scope of this documentation. For background information on the OAI-PMH, please refer to the official <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm" >OAI-PMH documentation</a> and to additional information and tutorials available through the <a href="http://www.openarchives.org">Open Archives Initiative</a>. </p> ! <p><a href="provider.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="directories"></a>Preparing files for serving</h3> ! <p>jOAI monitors each directory of files that is configured in the system and automatically adds, updates or deletes items from the OAI repository as files are added, updated or deleted from the directories. ! <c:choose> ! <c:when test="${rm.updateFrequency > 0}"> ! After the initial configuration, the synchronization between the files and the OAI repository occurs automatically every ! <%@ include file="../updateFrequency.jsp" %> ! or may be <a href="<c:url value='/admin/data-provider.do#index'/>">synchronized manually</a> at any time. ! </c:when> ! </c:choose> ! ! ! ! </p> ! <p>To ensure proper operation, files must follow these conventions: </p> ! <ul> ! <li>Each file must be a well-formed XML instance document.</li> ! <li>Each file must contain a single record, which corresponds to a single item in the OAI repository.</li> ! <li>All files within a given directory must be of the same metadata (XML) format.</li> ! <li>Each file name must end with a .xml file extension. </li> ! <li>The file name up to the .xml file extension must indicate a <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#UniqueIdentifier" >unique identifier</a> for the record*. For example, if the file is named <span class="code">abc-123.xml</span>, the identifier for the record will be <span class="code">abc-123</span> (the identifier is used as the local identifier portion of the <a href="http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm">OAI Identifier Format</a> in the OAI protocol). Identifiers in jOAI are <em>not</em> case sensitive. *Note that for files in the <span class="code">adn</span>, <span class="code">dlese_anno</span>, <span class="code">dlese_collect</span> and <span class="code">news_opps</span> formats, the file name is not used and instead the identifier must be indicated in the proper location in the file's XML.</li> ! <li>Identifiers must be unique across all files configured in the data provider. It is an error to have two or more files, regardless of format, with the same identifier.</li> ! <li>For network efficiency, the file modification date should change only when the content of the file is modified. Changing the modification date initiates a transfer of the record from the data provider to the harvester.</li> ! <li>To comply with the <a href="http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse">XML response format</a> required by the OAI protocol, encoding of the XML must use the UTF-8 representation of Unicode and character references, rather than entity references, must be used. </li> ! </ul> ! <p><a href="provider.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="convertors"></a>Providing files in multiple formats </h3> ! <p>jOAI can disseminate any given metadata file in multiple formats. For example, a file that resides in the <span class="code">adn</span> format can also be disseminated to harvesters in the <span class="code">oai_dc</span> format. This is done using metadata format converters. Several metadata format converters come pre-configured in the software as detailed below. New converters can be configured and implemented using an XSL stylesheet or a custom Java class that converts metadata from its native XML format to another XML format. Once a format converter is configured, all files in the native format will be disseminated in either the native or converted format depending on which format is requested by the harvester. </p> ! <p>The software comes pre-configured with the following metadata format converters:</p> ! <table border="1" cellspacing="0" cellpadding="0"> ! <tr> ! <td><strong>Native XML format </strong></td> ! <td><strong>Converted XML format </strong></td> ! </tr> ! <tr> ! <td class="code">nsdl_dc </td> ! <td class="code">oai_dc </td> ! </tr> ! <tr> ! <td class="code">adn </td> ! <td><span class="code">oai_dc</span>, <span class="code">nsdl_dc</span>, <span class="code">briefmeta</span> </td> ! </tr> ! <tr> ! <td class="code">dlese_anno </td> ! <td class="code">oai_dc </td> ! </tr> ! <tr> ! <td class="code">dlese_collect </td> ! <td class="code">oai_dc </td> ! </tr> ! <tr> ! <td class="code">news_opps </td> ! <td class="code">oai_dc </td> ! </tr> ! </table> ! <p>To configure additional metadata format converters, do the following: </p> ! <p>1. Create or obtain an XSL stylesheet or Java class that performs the desired format conversion from one XML format to another. The converter takes XML in the native format as its input and must generate XML in the converted format as its output. For Java converters, the class must implement the <a href="<c:url value='/docs/javadoc/org/dlese/dpc/xml/XMLFormatConverter.html'/>" class="code">XMLFormatConverter</a> Interface. </p> ! <p>2. If using an XSL stylesheet to perform the conversion, place it in the "xsl_files" directory located in the "WEB-INF" directory of the OAI software context. If using a Java class to perform the conversion, place the class binary anywhere within the classpath of the servlet container. </p> ! <p>3. Edit the"web.xml" file located in the "WEB-INF" directory and add a context-param element to configure each format converter (see the existing ones for examples).When configuring an XSL converter, the param-name element must start with the string with "xslconverter," followed by additional descriptive text. When configuring a Java class converter, the param-name element must start with the string with "javaconverter," followed by additional descriptive text. Each param-name must be unique; otherwise it will not be recognized. ! <p>For the param-value field, supply a string of the form ! <p class="code">[convertername] | [from format] | [to format] ! <p>where convertername is either the name of an XSL file or a fully qualified Java class and the "to" and "from" formats are metadataPrefixes for the given formats. </p> ! <p>For example, an XSL stylesheet named myDCConverter.xsl that converts from ADN to Dublin Core, the param-value would be </p> ! <p>"<span class="code">myDCConverter.xsl|adn|oai_dc</span>" (quotes omitted). </p> ! <p>For a Java class converter by the full name org.institution.converter.MyDCConverter, the param-value would be </p> ! <p>"<span class="code">org.institution.converter.MyDCConverter|adn|oai_dc</span>" (quotes omitted).</p> ! <p>An example of a complete context-param configuration for a format converter looks like the following:</p> ! ! <pre class="code"> ! <context-param> ! <param-name>xslconverter - adn to oai_dc converter</param-name> ! <param-value>adn-v0.6.50-to-oai_dc.xsl|adn|oai_dc</param-value> ! </context-param> </pre> ! <p>4. After configuring the web.xml file and placing the converter in the appropriate location, start or restart the software. The software automatically recognizes the converter and adds the new format to its list of available formats and exposed in response to the OAI <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#ListMetadataFormats" class="code">ListMetadataFormats</a> request. </p> ! <p>Tip: The format converter module caches the converted metadata to disk for ! increased performance. These converted files may be accessed locally. Accessed ! files are cached in the "WEB-INF/repository_data/converted_xml_cache" ! directory. </p> ! <p><a href="provider.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <c:import url="../bottom.jsp"/> ! </body> ! </html> ! |
|
From: John W. <jwe...@us...> - 2007-01-23 20:08:47
|
Update of /cvsroot/dlese/oai-project/web/WEB-INF/xsl_files In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv27958 Modified Files: adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl Log Message: updated xform Index: adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl =================================================================== RCS file: /cvsroot/dlese/oai-project/web/WEB-INF/xsl_files/adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl 18 Jan 2007 22:46:16 -0000 1.2 --- adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl 23 Jan 2007 20:08:41 -0000 1.3 *************** *** 1,2494 **** ! <?xml version="1.0"?> ! <xsl:stylesheet ! xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ! xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance" ! xmlns:d="http://adn.dlese.org" ! xmlns:dc="http://purl.org/dc/elements/1.1/" ! xmlns:nsdl_dc="http://ns.nsdl.org/nsdl_dc_v1.02/" ! xmlns:dct="http://purl.org/dc/terms/" ! xmlns:ieee="http://www.ieee.org/xsd/LOMv1p0" ! xmlns:ws="http://www.dlese.org/Metadata/ddsws" [...4933 lines suppressed...] ! <xsl:text>application/x-compress</xsl:text> ! </xsl:when> ! ! <xsl:when test="contains($lowercase, '.z')"> ! <xsl:text>application/x-compress</xsl:text> ! </xsl:when> ! ! <xsl:when test="contains($lowercase, '.zip')"> ! <xsl:attribute name="xsi:type">dct:IMT</xsl:attribute> ! <xsl:text>application/zip</xsl:text> ! </xsl:when> ! ! <xsl:otherwise> ! <xsl:attribute name="xsi:type">dct:IMT</xsl:attribute> ! <xsl:text>text/html</xsl:text> ! </xsl:otherwise> ! </xsl:choose> ! </xsl:element> ! </xsl:template> ! </xsl:stylesheet> |
|
From: John W. <jwe...@us...> - 2007-01-20 00:20:55
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv14140/web/docs Modified Files: CHANGES.txt Log Message: -upped version Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.32 retrieving revision 1.33 diff -C2 -r1.32 -r1.33 *** CHANGES.txt 19 Jan 2007 18:21:31 -0000 1.32 --- CHANGES.txt 20 Jan 2007 00:20:51 -0000 1.33 *************** *** 6,9 **** --- 6,14 ---- + v3.0.9 + + -Added nsdl_dc to oai_dc xsl crosswalk + + v3.0.8 (Released Jan 19, 2007) |
|
From: John W. <jwe...@us...> - 2007-01-20 00:20:55
|
Update of /cvsroot/dlese/oai-project In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv14140 Modified Files: build.xml Log Message: -upped version Index: build.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/build.xml,v retrieving revision 1.68 retrieving revision 1.69 diff -C2 -r1.68 -r1.69 *** build.xml 17 Jan 2007 19:42:50 -0000 1.68 --- build.xml 20 Jan 2007 00:20:51 -0000 1.69 *************** *** 96,100 **** <property name="app.name" value="oai"/> ! <property name="app.version" value="3.0.8"/> <property name="oai.context.name" value="oai"/> <property name="deploy.context.name" value="${oai.context.name}"/> --- 96,100 ---- <property name="app.name" value="oai"/> ! <property name="app.version" value="3.0.9"/> <property name="oai.context.name" value="oai"/> <property name="deploy.context.name" value="${oai.context.name}"/> |
|
From: John W. <jwe...@us...> - 2007-01-20 00:17:46
|
Update of /cvsroot/dlese/oai-project/web/WEB-INF/xsl_files In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv13013/web/WEB-INF/xsl_files Added Files: nsdl_dc2oai_dc.xsl nsdl_dc2oai_dc2.xsl Log Message: Added nsdl_dc to oai_dc xsl crosswalk contributed by Tim Cornwell and Naomi Dushay, NSDL/Cornell --- NEW FILE --- <?xml version="1.0" encoding="UTF-8"?> <!-- ============================================================= "nsdl_dc2oai_dc" stylesheet transform nsdl_dc v1.0.2 metadata to oai_dc by dumbing down Qualified Dublin Core Refinements to their equivalent simple DC elements; leaving the simple DC elements alone, and dropping all other elements. Looks for explicitly named elements in nsdl_dc and xforms them. Authors: Tim Cornwell and Naomi Dushay Created: 03/17/06 ================================================================ --> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:nsdl_dc="http://ns.nsdl.org/nsdl_dc_v1.02/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dct="http://purl.org/dc/terms/" xmlns:ieee="http://www.ieee.org/xsd/LOMv1p0" exclude-result-prefixes="#default nsdl_dc dct ieee"> <xsl:output method="xml" encoding="UTF-8" indent="yes" media-type="text/xml" /> <xsl:strip-space elements="*"/> <xsl:template match="nsdl_dc:nsdl_dc"> <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"> <xsl:apply-templates select="./*" /> </oai_dc:dc> </xsl:template> <!-- simple dc elements that have no refinements (they may have encoding schemes, but that doesn't affect the element name --> <xsl:template match="dc:contributor | dc:creator | dc:language | dc:publisher | dc:source | dc:subject | dc:type"> <!-- Note: this approach outputs dct and nsdl_dc namespace declarations in XMLSpy <xsl:copy> <xsl:value-of select="."/> </xsl:copy> --> <xsl:element name="dc:{local-name()}"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- simple dc elements that have refinements --> <!-- coverage --> <xsl:template match="dc:coverage | dct:spatial | dct:temporal"> <xsl:element name="dc:coverage"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- date --> <xsl:template match="dc:date | dct:available | dct:created | dct:dateAccepted | dct:dateCopyrighted | dct:dateSubmitted | dct:issued | dct:modified | dct:valid"> <xsl:element name="dc:date"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- description --> <xsl:template match = "dc:description | dct:abstract | dct:tableOfContents"> <xsl:element name="dc:description"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- format --> <xsl:template match="dc:format | dct:extent | dct:medium"> <xsl:element name="dc:format"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- identifier --> <xsl:template match="dc:identifier | dct:bibliographicCitation"> <xsl:element name="dc:identifier"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- relation --> <xsl:template match="dc:relation | dct:conformsTo | dct:hasFormat | dct:hasPart | dct:hasVersion | dct:isFormatOf | dct:isPartOf | dct:isReferencedBy | dct:isReplacedBy | dct:isRequiredBy | dct:isVersionOf | dct:references | dct:replaces | dct:requires"> <xsl:element name="dc:relation"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- rights --> <xsl:template match="dc:rights | dct:accessRights | dct:license"> <xsl:element name="dc:rights"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- title --> <xsl:template match="dc:title | dct:alternative"> <xsl:element name="dc:title"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- dc terms elements that are not strictly refinements of dc elements--> <!-- accessibility --> <xsl:template match="dct:accessibility"> </xsl:template> <!-- accrualMethod --> <xsl:template match="dct:accrualMethod"> </xsl:template> <!-- accrualPeriodicity --> <xsl:template match="dct:accrualPeriodicity"> </xsl:template> <!-- accrualPolicy --> <xsl:template match="dct:accrualPolicy"> </xsl:template> <!-- audience --> <xsl:template match="dct:audience"> </xsl:template> <xsl:template match="dct:educationLevel"> </xsl:template> <xsl:template match="dct:mediator"> </xsl:template> <!-- instructionalMethod --> <xsl:template match="dct:instructionalMethod"> </xsl:template> <!-- provenance --> <xsl:template match="dct:provenance"> </xsl:template> <!-- rightsHolder --> <xsl:template match="dct:rightsHolder"> </xsl:template> <!-- ieee elements --> <!-- interactivityLevel --> <xsl:template match="ieee:interactivityLevel"> </xsl:template> <!-- interactivityType --> <xsl:template match="ieee:interactivityType"> </xsl:template> <!-- typicalLearningTime --> <xsl:template match="ieee:typicalLearningTime"> </xsl:template> </xsl:stylesheet> --- NEW FILE --- <?xml version="1.0" encoding="UTF-8"?> <!-- ============================================================= "nsdl_dc2oai_dc2" stylesheet transform nsdl_dc v1.0.2 metadata to oai_dc by dumbing down Qualified Dublin Core Refinements to their equivalent simple DC elements; leaving the simple DC elements alone, and dropping all other elements. Uses the substitutionGroup attributes from the XML Schema to find the equivalent simple DC elements for the refined elements. based on Tom Habing's stylesheet at http://dli.grainger.uiuc.edu/publications/metadatacasestudy/dc_schemas/DCDD2.xsl <dc:title>DCDD2.xsl, th...@ui...</dc:title> <dc:creator>Tom Habing</dc:creator> <dc:date>2002-07-08</dc:date> Author: Naomi Dushay Created: 03/17/06 ================================================================ --> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:nsdl_dc="http://ns.nsdl.org/nsdl_dc_v1.02/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dct="http://purl.org/dc/terms/" xmlns:ieee="http://www.ieee.org/xsd/LOMv1p0" exclude-result-prefixes="#default xsi nsdl_dc oai_dc dct ieee"> <xsl:output method="xml" encoding="UTF-8" indent="yes" media-type="text/xml"/> <xsl:variable name="DCTERMS_SCHEMA" select="document('http://ns.nsdl.org/schemas/dc/dcterms_v1.01.xsd')"/> <xsl:template match="nsdl_dc:nsdl_dc"> <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"> <xsl:apply-templates select="./*" /> </oai_dc:dc> </xsl:template> <xsl:template match="dct:*"> <xsl:if test="$DCTERMS_SCHEMA//xs:element[@name=local-name(current())]"> <xsl:variable name="substitutionGroup" select="$DCTERMS_SCHEMA//xs:element[@name=local-name(current())]/@substitutionGroup" /> <xsl:if test="$substitutionGroup != 'dc:any' and starts-with($substitutionGroup, 'dc')"> <xsl:element namespace="http://purl.org/dc/elements/1.1/" name="{$substitutionGroup}"> <xsl:value-of select="."/> </xsl:element> </xsl:if> </xsl:if> </xsl:template> <xsl:template match="dc:*"> <!-- Note: this approach outputs dct and nsdl_dc namespace declarations in XMLSpy <xsl:copy> <xsl:value-of select="."/> </xsl:copy> --> <xsl:element name="dc:{local-name()}"> <xsl:value-of select="."/> </xsl:element> </xsl:template> <!-- no mapping from nsdl_dc's ieee elements to Simple DC elements --> <xsl:template match="ieee:*"> </xsl:template> </xsl:stylesheet> |
|
From: John W. <jwe...@us...> - 2007-01-20 00:17:45
|
Update of /cvsroot/dlese/oai-project/web/WEB-INF In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv13013/web/WEB-INF Modified Files: web.xml Log Message: Added nsdl_dc to oai_dc xsl crosswalk contributed by Tim Cornwell and Naomi Dushay, NSDL/Cornell Index: web.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/web/WEB-INF/web.xml,v retrieving revision 1.67 retrieving revision 1.68 diff -C2 -r1.67 -r1.68 *** web.xml 18 Jan 2007 22:46:16 -0000 1.67 --- web.xml 20 Jan 2007 00:17:41 -0000 1.68 *************** *** 148,152 **** <param-value>adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl|adn|nsdl_dc</param-value> </context-param> ! <!-- To configure a format converter that uses a Java class, the param-name must begin with --- 148,155 ---- <param-value>adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl|adn|nsdl_dc</param-value> </context-param> ! <context-param> ! <param-name>xslconverter - nsdl_dc to oai_dc converter</param-name> ! <param-value>nsdl_dc2oai_dc.xsl|nsdl_dc|oai_dc</param-value> ! </context-param> <!-- To configure a format converter that uses a Java class, the param-name must begin with |
|
From: John W. <jwe...@us...> - 2007-01-19 18:49:11
|
Update of /cvsroot/dlese/oai-project/web/admin In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv25495/web/admin Modified Files: display_harvester_settings.jsp Log Message: fixed erronous text at top of page Index: display_harvester_settings.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/admin/display_harvester_settings.jsp,v retrieving revision 1.50 retrieving revision 1.51 diff -C2 -r1.50 -r1.51 *** display_harvester_settings.jsp 16 Jan 2007 03:15:40 -0000 1.50 --- display_harvester_settings.jsp 19 Jan 2007 18:49:07 -0000 1.51 *************** *** 1,282 **** ! past harvests performed <%@ page language="java" %> ! <%-- <jsp:useBean id="haf" class="org.dlese.dpc.oai.harvester.action.form.HarvesterAdminForm" scope="request"/> --%> ! <%@ taglib uri="/WEB-INF/tlds/struts-html.tld" prefix="html" %> ! <%@ taglib uri="/WEB-INF/tlds/struts-logic.tld" prefix="logic" %> ! <!-- JSTL tags --> ! <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> ! <%@ page isELIgnored ="false" %> ! ! <html:html> ! ! <head> ! <title>jOAI Harvester Setup and Status</title> ! ! <!-- Step ONE : IMPORT "head.jsp" --> ! <c:import url="../head.jsp"/> ! </head> ! ! <body> ! <!-- STEP TWO: IMPORT "top.jsp" --> ! <c:import url="../top.jsp?sec=harvester"/> ! ! <!-- CONTENT GOES HERE --> ! ! <h1>Harvester Setup and Status</h1> ! ! <%-- ######## Display messages, if present ######## --%> ! <logic:messagesPresent> ! <table width="100%" bgcolor="#000000" cellspacing="1" cellpadding="8"> ! <tr bgcolor="ffffff"> ! <td> ! <ul> ! <html:messages id="msg" property="message"> ! <li><c:out value="${msg}" /></li> ! </html:messages> ! <html:messages id="msg" property="error"> ! <li><font color=red>Error: <c:out value="${msg}" /></font></li> ! </html:messages> ! <html:messages id="msg" property="harvestErr"> ! <li><c:out value="${msg}" /></li> ! </html:messages> ! <html:messages id="msg" property="runHarvest"> ! <li><c:out value="${msg}" /></li> ! <li>Click to <a href='harvestreport.do?q=uid:<c:out value="${haf.lastRunHarvest.uid}" />&s=0&report=History+and+status+of+harvests+for+<c:out value="${haf.lastRunHarvest.baseURL}" />'>view the harvest status report for this harvest</a></li> ! </html:messages> ! <html:messages id="msg" property="runOneTimeHarvest"> ! <li><c:out value="${msg}" /></li> ! <li>Click to <a href='harvestreport.do?q=uid:<c:out value="${haf.lastOneTimeHarvest.uid}" />&s=0&report=Most+recent+one-time+harvest'>view the harvest status report for this harvest</a></li> ! </html:messages> ! <logic:messagesPresent property="validationError"> ! <li><font color="red">Please fix the error(s) <a href="#oneTime">shown below</a> and click "Harvest" or ! <a href="harvester.do">Cancel.</a></font></li> ! </logic:messagesPresent> ! </ul> ! ! [ <a href="harvester.do">OK</a> ] ! ! </td> ! </tr> ! </table> ! <br><br> ! </logic:messagesPresent> ! ! <%-- <logic:messagesPresent property="harvestErr"> ! <html:messages id="msg" property="harvestErr"> ! <font color="red">Harvest result: <c:out value="${msg}" /></font><br><br> ! </html:messages> ! </logic:messagesPresent> --%> ! ! ! ! ! ! <c:set var="defdir"> ! <c:out value="${haf.defDir}" /> ! </c:set> ! ! <h3>Setup</h3> ! Add a harvest to get metadata XML files from OAI data providers. If only <em>providing</em> metadata files, harvester set up is not necessary.</p> ! <table width="84%" border="0"> ! <tr> ! <td width="14%"> ! <html:form action="/admin/harvester" ! method="GET"> ! <html:submit property="button" value="Add new harvest" /> Create a harvest to get files and to specify when and where the harvest is performed. ! <html:hidden property="scheduledHarvest" value="add"/> ! </html:form></td> ! ! </tr> ! </table> ! ! ! <c:if test="${!empty haf.scheduledHarvests}"> ! ! <h3>Status</h3> ! <table border="0"> ! <tr> ! <td><INPUT name="BUTTON" TYPE="BUTTON" ONCLICK="window.location.href='harvestreport.do?q=doctype:0harvestlog+AND+!repositoryname:%22One+time+harvest%22&s=0&report=Harvest+History+and+Progress'" VALUE="View harvest history and progress"></td> ! <td><div align="left">View a listing of all past harvests performed, current harvests in progress and their details. </div></td> ! </tr> ! </table> <br> ! ! <%-- <p>Records from harvests will be saved in directories by baseURL, set and format inside the following directory:<br> ! <c:out value="${haf.shHarvestedDataDir}" /> [ <a href="harvester.do?editShHarvestedDataDir=edit">Edit</a> ] ! </p>--%> ! <table id="form" cellpadding="6" cellspacing="1" width="100%" border="0"> ! ! <tr id="headrow"> ! <td width="34%"> <div align="center"><b>Harvest Repository</b></div></td> ! <td width="14%"> <div align="center"><b>Metadata<br> ! Format</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_format')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>SetSpec</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_setspec')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>Harvest Interval</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_interval')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>Manually<br>Harvest</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_manual')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>Harvest Settings</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_settings')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! </tr> ! ! <c:forEach var="scheduledHarvest" items="${haf.scheduledHarvests}"> ! ! <c:set var="zipped"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.zipLatest}" /> ! </c:set> ! ! <c:set var="emptyzipped"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/ ! </c:set> ! ! ! <c:set var="one"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.backupOne}" /> ! </c:set> ! <c:set var="two"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.backupTwo}" /> ! </c:set> ! <c:set var="three"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.backupThree}" /> ! </c:set> ! <c:set var="numH"> ! <c:out value="${scheduledHarvest.numHarvestedLast}"/> ! </c:set> ! ! <c:set var="warn"> ! <c:out value="${scheduledHarvest.warnR}" /> ! </c:set> ! ! ! ! ! ! ! <tr id="formrow"> ! <td width="34%"><table width="100%" border="0" cellspacing="4"> ! <tr> ! <td><b> ! <c:out value="${scheduledHarvest.repositoryName}" /> ! </b></td> ! </tr> ! <tr> ! <td><b>Base URL</b>: ! <c:out value="${scheduledHarvest.baseURL}" /> ! <br> ! <b>Harvested to</b>: ! <c:out value="${scheduledHarvest.harvestDir}" /> ! <br> ! <c:if test='${scheduledHarvest.lastHarvestTime != null}'> <b>Last harvest: </b> ! <c:out value="${numH}" /> ! files, ! <c:out value="${scheduledHarvest.lastHarvestTime}" /> ! <br> ! </c:if> ! <c:if test='${scheduledHarvest.isZipPresent == "true"}'> ! <c:if test="${zipped != emptyzipped}"><b>Download zipped harvest</b>: ! <c:choose> ! <c:when test='${warn}'> ! <a href="javascript:more('<c:out value="${zipped}"/>', '<c:out value="${scheduledHarvest.harvestDir}" />')">Most recent </a></c:when> ! <c:otherwise> <a href="${zipped}">Most recent</a> </c:otherwise> ! </c:choose> ! <c:choose> ! <c:when test='${scheduledHarvest.backupTwo == ""}'> </c:when> ! <c:otherwise> | ! <c:choose> ! <c:when test='${warn}'> <a href="javascript:more('<c:out value="${two}"/>', ' ! <c:out value="${scheduledHarvest.harvestDir}" /> ! ')">Older </a></c:when> ! <c:otherwise> <a href="${two}">Older</a> </c:otherwise> ! </c:choose> ! <c:choose> ! <c:when test='${scheduledHarvest.backupThree == ""}'> </c:when> ! <c:otherwise> | ! <c:choose> ! <c:when test='${warn}'> <a href="javascript:more('<c:out value="${three}"/>', ' ! <c:out value="${scheduledHarvest.harvestDir}" /> ! ')">Oldest </a> </c:when> ! <c:otherwise> <a href="${three}">Oldest</a> </c:otherwise> ! </c:choose> ! </c:otherwise> ! </c:choose> ! ! </c:otherwise> ! </c:choose> ! <br> ! </c:if> ! </c:if> ! <a href='harvestreport.do?q=uid:<c:out value="${scheduledHarvest.uid}" />&s=0&report=Harvest+History+and+Progress+for+<c:out value="${scheduledHarvest.baseURL}" />'>View harvest history and progress</a></td> ! </tr> ! </table></td> ! <td width="14%"> ! <div align="center"> <c:out value="${scheduledHarvest.metadataPrefix}" /></div> </td> ! <td> ! <c:choose> ! <c:when test='${scheduledHarvest.setSpecHtml != " "}'> ! <div align="center"> <c:out value="${scheduledHarvest.setSpecHtml}" escapeXml="false"/> </div> ! </c:when> ! <c:otherwise> ! <div align="center"> -</div> ! </c:otherwise> ! </c:choose> </td> ! ! <td> ! <c:choose> ! <c:when test='${scheduledHarvest.enabledDisabled != "disabled"}'> ! <div align="center">Automatic<br> ! <c:choose> ! <c:when test="${not empty scheduledHarvest.runAtTime}"> ! (Every ${scheduledHarvest.harvestingInterval == 1 ? '' : scheduledHarvest.harvestingInterval} ${scheduledHarvest.intervalGranularityLabel} ! at ! <nobr>${scheduledHarvest.runAtTimeDisplay})</nobr> ! </c:when> ! <c:otherwise> ! (Every ${scheduledHarvest.harvestingInterval} ${scheduledHarvest.intervalGranularityLabel}) ! </c:otherwise> ! </c:choose> ! </div> ! </br> ! </c:when> ! <c:otherwise> ! <div align="center">Manual</div> ! </c:otherwise> ! </c:choose> </td> ! ! ! ! <td width="13%"> ! ! <div align="center"> <a href="javascript:confirmHref( ! 'harvester.do?scheduledHarvest=runHarvest&shUid=<c:out value="${scheduledHarvest.uid}" />&mySes=<c:out value="${haf.mySes}" />', ! 'Harvest <c:out value="${scheduledHarvest.repositoryNameEscaped}" /> now ! and request only those files that have changed since the last harvest?')" ! title="Harvest records that are new or updated since the previous harvest">New</a> | ! <a href="javascript:confirmHref( ! 'harvester.do?scheduledHarvest=runHarvest&doAll=t&shUid=<c:out value="${scheduledHarvest.uid}" />&mySes=<c:out value="${haf.mySes}" />', ! 'Harvest all files from <c:out value="${scheduledHarvest.repositoryNameEscaped}" /> and replace any existing files that were previously harvested?')" ! title="Harvest all records">All</a> <br></div> </td> ! ! <td width="13%"> ! <div align="center"> <a href="harvester.do?scheduledHarvest=edit&shUid=<c:out value="${scheduledHarvest.uid}" />" ! title="Edit these settings">Edit</a> | <a href="javascript:confirmHref( ! 'harvester.do?scheduledHarvest=delete&shUid=<c:out value="${scheduledHarvest.uid}" />', ! 'Are you sure you want to delete the harvest for <c:out value="${scheduledHarvest.repositoryNameEscaped}" />?')" ! title="Delete this scheduled harvest">Delete</a></div> </td> ! </tr> ! </c:forEach> ! </table> ! <br> ! </c:if> ! ! <c:if test="${!empty haf.scheduledHarvests}"> ! <html:form action="/admin/harvester" ! method="GET"> ! <html:submit property="button" value="Add new harvest" /> ! <html:hidden property="scheduledHarvest" value="add"/> ! </html:form> ! <INPUT name="BUTTON" TYPE="BUTTON" ONCLICK="window.location.href='harvestreport.do?q=doctype:0harvestlog+AND+!repositoryname:%22One+time+harvest%22&s=0&report=Harvest+History+and+Progress'" VALUE="View harvest history and progress"> ! </c:if> ! ! <!-- END OF YOUR CONTENT --> ! ! <!-- STEP THREE : IMPORT "bottom.jsp" --> ! <c:import url="../bottom.jsp"/> ! ! </body> ! </html:html> ! --- 1,282 ---- ! <%@ page language="java" %> ! <%-- <jsp:useBean id="haf" class="org.dlese.dpc.oai.harvester.action.form.HarvesterAdminForm" scope="request"/> --%> ! <%@ taglib uri="/WEB-INF/tlds/struts-html.tld" prefix="html" %> ! <%@ taglib uri="/WEB-INF/tlds/struts-logic.tld" prefix="logic" %> ! <!-- JSTL tags --> ! <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> ! <%@ page isELIgnored ="false" %> ! ! <html:html> ! ! <head> ! <title>jOAI Harvester Setup and Status</title> ! ! <!-- Step ONE : IMPORT "head.jsp" --> ! <c:import url="../head.jsp"/> ! </head> ! ! <body> ! <!-- STEP TWO: IMPORT "top.jsp" --> ! <c:import url="../top.jsp?sec=harvester"/> ! ! <!-- CONTENT GOES HERE --> ! ! <h1>Harvester Setup and Status</h1> ! ! <%-- ######## Display messages, if present ######## --%> ! <logic:messagesPresent> ! <table width="100%" bgcolor="#000000" cellspacing="1" cellpadding="8"> ! <tr bgcolor="ffffff"> ! <td> ! <ul> ! <html:messages id="msg" property="message"> ! <li><c:out value="${msg}" /></li> ! </html:messages> ! <html:messages id="msg" property="error"> ! <li><font color=red>Error: <c:out value="${msg}" /></font></li> ! </html:messages> ! <html:messages id="msg" property="harvestErr"> ! <li><c:out value="${msg}" /></li> ! </html:messages> ! <html:messages id="msg" property="runHarvest"> ! <li><c:out value="${msg}" /></li> ! <li>Click to <a href='harvestreport.do?q=uid:<c:out value="${haf.lastRunHarvest.uid}" />&s=0&report=History+and+status+of+harvests+for+<c:out value="${haf.lastRunHarvest.baseURL}" />'>view the harvest status report for this harvest</a></li> ! </html:messages> ! <html:messages id="msg" property="runOneTimeHarvest"> ! <li><c:out value="${msg}" /></li> ! <li>Click to <a href='harvestreport.do?q=uid:<c:out value="${haf.lastOneTimeHarvest.uid}" />&s=0&report=Most+recent+one-time+harvest'>view the harvest status report for this harvest</a></li> ! </html:messages> ! <logic:messagesPresent property="validationError"> ! <li><font color="red">Please fix the error(s) <a href="#oneTime">shown below</a> and click "Harvest" or ! <a href="harvester.do">Cancel.</a></font></li> ! </logic:messagesPresent> ! </ul> ! ! [ <a href="harvester.do">OK</a> ] ! ! </td> ! </tr> ! </table> ! <br><br> ! </logic:messagesPresent> ! ! <%-- <logic:messagesPresent property="harvestErr"> ! <html:messages id="msg" property="harvestErr"> ! <font color="red">Harvest result: <c:out value="${msg}" /></font><br><br> ! </html:messages> ! </logic:messagesPresent> --%> ! ! ! ! ! ! <c:set var="defdir"> ! <c:out value="${haf.defDir}" /> ! </c:set> ! ! <h3>Setup</h3> ! Add a harvest to get metadata XML files from OAI data providers. If only <em>providing</em> metadata files, harvester set up is not necessary.</p> ! <table width="84%" border="0"> ! <tr> ! <td width="14%"> ! <html:form action="/admin/harvester" ! method="GET"> ! <html:submit property="button" value="Add new harvest" /> Create a harvest to get files and to specify when and where the harvest is performed. ! <html:hidden property="scheduledHarvest" value="add"/> ! </html:form></td> ! ! </tr> ! </table> ! ! ! <c:if test="${!empty haf.scheduledHarvests}"> ! ! <h3>Status</h3> ! <table border="0"> ! <tr> ! <td><INPUT name="BUTTON" TYPE="BUTTON" ONCLICK="window.location.href='harvestreport.do?q=doctype:0harvestlog+AND+!repositoryname:%22One+time+harvest%22&s=0&report=Harvest+History+and+Progress'" VALUE="View harvest history and progress"></td> ! <td><div align="left">View a listing of all past harvests performed, current harvests in progress and their details. </div></td> ! </tr> ! </table> <br> ! ! <%-- <p>Records from harvests will be saved in directories by baseURL, set and format inside the following directory:<br> ! <c:out value="${haf.shHarvestedDataDir}" /> [ <a href="harvester.do?editShHarvestedDataDir=edit">Edit</a> ] ! </p>--%> ! <table id="form" cellpadding="6" cellspacing="1" width="100%" border="0"> ! ! <tr id="headrow"> ! <td width="34%"> <div align="center"><b>Harvest Repository</b></div></td> ! <td width="14%"> <div align="center"><b>Metadata<br> ! Format</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_format')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>SetSpec</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_setspec')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>Harvest Interval</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_interval')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>Manually<br>Harvest</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_manual')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! <td width="13%"> <div align="center"><b>Harvest Settings</b><a href="javascript:popupHelp('<c:out value="${pageContext.request.contextPath}"/>','disp_settings')" class="helpp"> <img src='<c:out value="${pageContext.request.contextPath}" />/images/help.gif' border=0></a></div></td> ! </tr> ! ! <c:forEach var="scheduledHarvest" items="${haf.scheduledHarvests}"> ! ! <c:set var="zipped"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.zipLatest}" /> ! </c:set> ! ! <c:set var="emptyzipped"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/ ! </c:set> ! ! ! <c:set var="one"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.backupOne}" /> ! </c:set> ! <c:set var="two"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.backupTwo}" /> ! </c:set> ! <c:set var="three"> ! <c:out value="${pageContext.request.contextPath}"/>/${initParam.zippedHarvestsDirectory}/<c:out value="${scheduledHarvest.backupThree}" /> ! </c:set> ! <c:set var="numH"> ! <c:out value="${scheduledHarvest.numHarvestedLast}"/> ! </c:set> ! ! <c:set var="warn"> ! <c:out value="${scheduledHarvest.warnR}" /> ! </c:set> ! ! ! ! ! ! ! <tr id="formrow"> ! <td width="34%"><table width="100%" border="0" cellspacing="4"> ! <tr> ! <td><b> ! <c:out value="${scheduledHarvest.repositoryName}" /> ! </b></td> ! </tr> ! <tr> ! <td><b>Base URL</b>: ! <c:out value="${scheduledHarvest.baseURL}" /> ! <br> ! <b>Harvested to</b>: ! <c:out value="${scheduledHarvest.harvestDir}" /> ! <br> ! <c:if test='${scheduledHarvest.lastHarvestTime != null}'> <b>Last harvest: </b> ! <c:out value="${numH}" /> ! files, ! <c:out value="${scheduledHarvest.lastHarvestTime}" /> ! <br> ! </c:if> ! <c:if test='${scheduledHarvest.isZipPresent == "true"}'> ! <c:if test="${zipped != emptyzipped}"><b>Download zipped harvest</b>: ! <c:choose> ! <c:when test='${warn}'> ! <a href="javascript:more('<c:out value="${zipped}"/>', '<c:out value="${scheduledHarvest.harvestDir}" />')">Most recent </a></c:when> ! <c:otherwise> <a href="${zipped}">Most recent</a> </c:otherwise> ! </c:choose> ! <c:choose> ! <c:when test='${scheduledHarvest.backupTwo == ""}'> </c:when> ! <c:otherwise> | ! <c:choose> ! <c:when test='${warn}'> <a href="javascript:more('<c:out value="${two}"/>', ' ! <c:out value="${scheduledHarvest.harvestDir}" /> ! ')">Older </a></c:when> ! <c:otherwise> <a href="${two}">Older</a> </c:otherwise> ! </c:choose> ! <c:choose> ! <c:when test='${scheduledHarvest.backupThree == ""}'> </c:when> ! <c:otherwise> | ! <c:choose> ! <c:when test='${warn}'> <a href="javascript:more('<c:out value="${three}"/>', ' ! <c:out value="${scheduledHarvest.harvestDir}" /> ! ')">Oldest </a> </c:when> ! <c:otherwise> <a href="${three}">Oldest</a> </c:otherwise> ! </c:choose> ! </c:otherwise> ! </c:choose> ! ! </c:otherwise> ! </c:choose> ! <br> ! </c:if> ! </c:if> ! <a href='harvestreport.do?q=uid:<c:out value="${scheduledHarvest.uid}" />&s=0&report=Harvest+History+and+Progress+for+<c:out value="${scheduledHarvest.baseURL}" />'>View harvest history and progress</a></td> ! </tr> ! </table></td> ! <td width="14%"> ! <div align="center"> <c:out value="${scheduledHarvest.metadataPrefix}" /></div> </td> ! <td> ! <c:choose> ! <c:when test='${scheduledHarvest.setSpecHtml != " "}'> ! <div align="center"> <c:out value="${scheduledHarvest.setSpecHtml}" escapeXml="false"/> </div> ! </c:when> ! <c:otherwise> ! <div align="center"> -</div> ! </c:otherwise> ! </c:choose> </td> ! ! <td> ! <c:choose> ! <c:when test='${scheduledHarvest.enabledDisabled != "disabled"}'> ! <div align="center">Automatic<br> ! <c:choose> ! <c:when test="${not empty scheduledHarvest.runAtTime}"> ! (Every ${scheduledHarvest.harvestingInterval == 1 ? '' : scheduledHarvest.harvestingInterval} ${scheduledHarvest.intervalGranularityLabel} ! at ! <nobr>${scheduledHarvest.runAtTimeDisplay})</nobr> ! </c:when> ! <c:otherwise> ! (Every ${scheduledHarvest.harvestingInterval} ${scheduledHarvest.intervalGranularityLabel}) ! </c:otherwise> ! </c:choose> ! </div> ! </br> ! </c:when> ! <c:otherwise> ! <div align="center">Manual</div> ! </c:otherwise> ! </c:choose> </td> ! ! ! ! <td width="13%"> ! ! <div align="center"> <a href="javascript:confirmHref( ! 'harvester.do?scheduledHarvest=runHarvest&shUid=<c:out value="${scheduledHarvest.uid}" />&mySes=<c:out value="${haf.mySes}" />', ! 'Harvest <c:out value="${scheduledHarvest.repositoryNameEscaped}" /> now ! and request only those files that have changed since the last harvest?')" ! title="Harvest records that are new or updated since the previous harvest">New</a> | ! <a href="javascript:confirmHref( ! 'harvester.do?scheduledHarvest=runHarvest&doAll=t&shUid=<c:out value="${scheduledHarvest.uid}" />&mySes=<c:out value="${haf.mySes}" />', ! 'Harvest all files from <c:out value="${scheduledHarvest.repositoryNameEscaped}" /> and replace any existing files that were previously harvested?')" ! title="Harvest all records">All</a> <br></div> </td> ! ! <td width="13%"> ! <div align="center"> <a href="harvester.do?scheduledHarvest=edit&shUid=<c:out value="${scheduledHarvest.uid}" />" ! title="Edit these settings">Edit</a> | <a href="javascript:confirmHref( ! 'harvester.do?scheduledHarvest=delete&shUid=<c:out value="${scheduledHarvest.uid}" />', ! 'Are you sure you want to delete the harvest for <c:out value="${scheduledHarvest.repositoryNameEscaped}" />?')" ! title="Delete this scheduled harvest">Delete</a></div> </td> ! </tr> ! </c:forEach> ! </table> ! <br> ! </c:if> ! ! <c:if test="${!empty haf.scheduledHarvests}"> ! <html:form action="/admin/harvester" ! method="GET"> ! <html:submit property="button" value="Add new harvest" /> ! <html:hidden property="scheduledHarvest" value="add"/> ! </html:form> ! <INPUT name="BUTTON" TYPE="BUTTON" ONCLICK="window.location.href='harvestreport.do?q=doctype:0harvestlog+AND+!repositoryname:%22One+time+harvest%22&s=0&report=Harvest+History+and+Progress'" VALUE="View harvest history and progress"> ! </c:if> ! ! <!-- END OF YOUR CONTENT --> ! ! <!-- STEP THREE : IMPORT "bottom.jsp" --> ! <c:import url="../bottom.jsp"/> ! ! </body> ! </html:html> ! |
|
From: John W. <jwe...@us...> - 2007-01-19 18:21:36
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv15351/web/docs Modified Files: CHANGES.txt product_release_config.xml Log Message: added v3.0.8 release info Index: CHANGES.txt =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/CHANGES.txt,v retrieving revision 1.31 retrieving revision 1.32 diff -C2 -r1.31 -r1.32 *** CHANGES.txt 17 Jan 2007 19:42:50 -0000 1.31 --- CHANGES.txt 19 Jan 2007 18:21:31 -0000 1.32 *************** *** 6,10 **** ! v3.0.8 -Fixed bug in the data provider where sometimes empty content was returned in --- 6,10 ---- ! v3.0.8 (Released Jan 19, 2007) -Fixed bug in the data provider where sometimes empty content was returned in *************** *** 16,20 **** ! v3.0.7 (Released Jan 16, 2007) -Improved performace of the Harvester. Fixed bug that caused the harvester --- 16,20 ---- ! v3.0.7 -Improved performace of the Harvester. Fixed bug that caused the harvester Index: product_release_config.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/product_release_config.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -r1.6 -r1.7 *** product_release_config.xml 16 Jan 2007 04:32:47 -0000 1.6 --- product_release_config.xml 19 Jan 2007 18:21:31 -0000 1.7 *************** *** 1,136 **** ! <productReleases> ! <!-- ! This configuration file is used to generate a page with information and liks for jOAI ! downloads. The JSP page that does the rendering is in the services area of the ! dds-project (/services/joai_software.jsp). ! This config should be installed at http://www.dlese.org/downloads/joai/product_release_config.xml. ! To add a new release, copy a <release> element and replace the information ! as appropriate. The current release is always the first one. ! --> ! <package id="joai"> ! <name>jOAI Software Download</name> ! <description> ! <![CDATA[ ! jOAI is a Java-based open source <a href="http://www.openarchives.org/" target="_blank">Open Archives Initiative</a> ! data provider and harvester tool that runs in a ! servlet container such as <a href="http://tomcat.apache.org/" target="_blank">Apache Tomcat</a>. ! ! <br/><br/> ! ! <a href="http://www.dlese.org/oai/docs/provider.jsp">The jOAI data provider</a> allows XML files from a file system to be ! exposed as items in an OAI data repository and made available for harvesting by others using the OAI-PMH. After ! pointing the software to one or more file directories, the software monitors the XML files inside, adding, ! updating or deleting them from the OAI repository as files are added, updated or deleted from the directories. ! ! <br/><br/> ! ! <a href="http://www.dlese.org/oai/docs/harvester.jsp">The jOAI harvester</a> is used to retrieve metadata records ! from remote OAI data providers and save them to the local file system, one record per file. In addition, ! records that have been harvested are packaged into zip archives that can be downloaded and opened through ! the harvester's web-based interface. ! ! <br/><br/> ! ! The software is developed by the ! <a href="http://www.ucar.edu/" target="_blank">University Corporation for Atmospheric Research</a> (UCAR), ! DLESE Program Center. jOAI can be installed on Windows, Linux, Mac OS or UNIX systems. ! ]]> ! </description> ! <release version="3.0.7"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.7/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.7/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.7/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.7/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.7+Binary&url=/downloads/joai/v3.0.7/joai_v3.0.7.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.7+Source&url=/downloads/joai/v3.0.7/joai_v3.0.7_source.zip</url> ! </link> ! </release> ! <release version="3.0.6"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.6/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.6/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.6/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.6/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.6+Binary&url=/downloads/joai/v3.0.6/joai_v3.0.6.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.6+Source&url=/downloads/joai/v3.0.6/joai_v3.0.6_source.zip</url> ! </link> ! </release> ! <release version="3.0.4"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.4/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.4/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.4/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.4/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.4+Binary&url=/downloads/joai/v3.0.4/joai_v3.0.4.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.4+Source&url=/downloads/joai/v3.0.4/joai_v3.0.4_source.zip</url> ! </link> ! </release> ! <release version="3.0.2"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.2/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.2/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.2/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.2/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.2+Binary&url=/downloads/joai/v3.0.2/joai_v3.0.2.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.2+Source&url=/downloads/joai/v3.0.2/joai_v3.0.2_source.zip</url> ! </link> ! </release> ! <release version="2.0.9.3"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v2.0.9.3/README.txt">changes in this version</a>, ! <a href="/downloads/joai/v2.0.9.3/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v2.0.9.3/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v2.0.9.3/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?url=/downloads/joai/v2.0.9.3/dlese_oai_v2.0.9.3.zip&package=jOAI+v2.0.9.3+Binary</url> ! ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?url=/downloads/joai/v2.0.9.3/dlese_oai_v2.0.9.3_source.zip&package=jOAI+v2.0.9.3+Source</url> ! </link> ! </release> ! </package> ! </productReleases> --- 1,136 ---- ! <productReleases> ! <!-- ! This configuration file is used to generate a page with information and liks for jOAI ! downloads. The JSP page that does the rendering is in the services area of the ! dds-project (/services/joai_software.jsp). ! This config should be installed at http://www.dlese.org/downloads/joai/product_release_config.xml. ! To add a new release, copy a <release> element and replace the information ! as appropriate. The current release is always the first one. ! --> ! <package id="joai"> ! <name>jOAI Software Download</name> ! <description> ! <![CDATA[ ! jOAI is a Java-based open source <a href="http://www.openarchives.org/" target="_blank">Open Archives Initiative</a> ! data provider and harvester tool that runs in a ! servlet container such as <a href="http://tomcat.apache.org/" target="_blank">Apache Tomcat</a>. ! ! <br/><br/> ! ! <a href="http://www.dlese.org/oai/docs/provider.jsp">The jOAI data provider</a> allows XML files from a file system to be ! exposed as items in an OAI data repository and made available for harvesting by others using the OAI-PMH. After ! pointing the software to one or more file directories, the software monitors the XML files inside, adding, ! updating or deleting them from the OAI repository as files are added, updated or deleted from the directories. ! ! <br/><br/> ! ! <a href="http://www.dlese.org/oai/docs/harvester.jsp">The jOAI harvester</a> is used to retrieve metadata records ! from remote OAI data providers and save them to the local file system, one record per file. In addition, ! records that have been harvested are packaged into zip archives that can be downloaded and opened through ! the harvester's web-based interface. ! ! <br/><br/> ! ! The software is developed by the ! <a href="http://www.ucar.edu/" target="_blank">University Corporation for Atmospheric Research</a> (UCAR), ! DLESE Program Center. jOAI can be installed on Windows, Linux, Mac OS or UNIX systems. ! ]]> ! </description> ! <release version="3.0.8"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.8/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.8/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.8/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.8/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.8+Binary&url=/downloads/joai/v3.0.8/joai_v3.0.8.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.8+Source&url=/downloads/joai/v3.0.8/joai_v3.0.8_source.zip</url> ! </link> ! </release> ! <release version="3.0.6"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.6/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.6/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.6/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.6/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.6+Binary&url=/downloads/joai/v3.0.6/joai_v3.0.6.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.6+Source&url=/downloads/joai/v3.0.6/joai_v3.0.6_source.zip</url> ! </link> ! </release> ! <release version="3.0.4"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.4/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.4/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.4/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.4/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.4+Binary&url=/downloads/joai/v3.0.4/joai_v3.0.4.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.4+Source&url=/downloads/joai/v3.0.4/joai_v3.0.4_source.zip</url> ! </link> ! </release> ! <release version="3.0.2"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v3.0.2/CHANGES.txt">changes in this version</a>, ! <a href="/downloads/joai/v3.0.2/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v3.0.2/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v3.0.2/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.2+Binary&url=/downloads/joai/v3.0.2/joai_v3.0.2.zip</url> ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?package=jOAI+3.0.2+Source&url=/downloads/joai/v3.0.2/joai_v3.0.2_source.zip</url> ! </link> ! </release> ! <release version="2.0.9.3"> ! <notes> ! <![CDATA[ ! See: ! <a href="/downloads/joai/v2.0.9.3/README.txt">changes in this version</a>, ! <a href="/downloads/joai/v2.0.9.3/INSTALL.txt">installation instructions</a>, ! <a href="/downloads/joai/v2.0.9.3/BUILD_INSTRUCTIONS.txt">building from source</a>, ! <a href="/downloads/joai/v2.0.9.3/LICENSE.txt">software license</a>. ! ]]> ! </notes> ! <link> ! <name>Download binary application</name> ! <url>/jsp/download/download.jsp?url=/downloads/joai/v2.0.9.3/dlese_oai_v2.0.9.3.zip&package=jOAI+v2.0.9.3+Binary</url> ! ! </link> ! <link> ! <name>Download source code</name> ! <url>/jsp/download/download.jsp?url=/downloads/joai/v2.0.9.3/dlese_oai_v2.0.9.3_source.zip&package=jOAI+v2.0.9.3+Source</url> ! </link> ! </release> ! </package> ! </productReleases> |
|
From: John W. <jwe...@us...> - 2007-01-18 22:46:20
|
Update of /cvsroot/dlese/oai-project/web/WEB-INF/xsl_files In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv2188/web/WEB-INF/xsl_files Modified Files: adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl Log Message: fixed the adn to nsdl_dc transform with ASN identifiers to work with the default Java 1.5 XSLT processor Index: adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl =================================================================== RCS file: /cvsroot/dlese/oai-project/web/WEB-INF/xsl_files/adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -r1.1 -r1.2 *** adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl 13 Jan 2007 01:04:44 -0000 1.1 --- adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl 18 Jan 2007 22:46:16 -0000 1.2 *************** *** 10,16 **** xmlns:ws="http://www.dlese.org/Metadata/ddsws" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ! exclude-result-prefixes="xsi d" version="1.0"> <!--ORGANIZATION OF THIS FILE--> <!-- **************************************--> --- 10,18 ---- xmlns:ws="http://www.dlese.org/Metadata/ddsws" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ! exclude-result-prefixes="xsi d dc nsdl_dc dct ieee" version="1.0"> + <!--exclude was xsi d; had to change it to the above to try to get this stylesheet working in Java 1.5--> + <!--ORGANIZATION OF THIS FILE--> <!-- **************************************--> *************** *** 623,628 **** --- 625,638 ---- + <!--VARIABLES used throughout the transform--> <!-- **********************************************************--> + <!--variable for adding a line return;--> + <xsl:variable name="newline"> + <xsl:text> + </xsl:text> + </xsl:variable> + + <!--variable for accessing DLESE webservice when given a DLESE library id--> <!--webservice 1-1 has namespaces unlike 1-1 so account for them--> *************** *** 655,661 **** <!-- **************************************--> <xsl:template match="d:itemRecord"> ! <xsl:element name="nsdl_dc:nsdl_dc" namespace="http://ns.nsdl.org/nsdl_dc_v1.02/"> <xsl:attribute name="schemaVersion">1.02.010</xsl:attribute> <xsl:attribute name="xsi:schemaLocation">http://ns.nsdl.org/nsdl_dc_v1.02/ http://ns.nsdl.org/schemas/nsdl_dc/nsdl_dc_v1.02.xsd</xsl:attribute> <!--dc:title--> --- 665,683 ---- <!-- **************************************--> <xsl:template match="d:itemRecord"> ! <!--excluding to use the text instruction below in order to make stylesheet work in Java 1.5 ! <xsl:element name="nsdl_dc:nsdl_dc" namespace="http://ns.nsdl.org/nsdl_dc_v1.02/" > <xsl:attribute name="schemaVersion">1.02.010</xsl:attribute> <xsl:attribute name="xsi:schemaLocation">http://ns.nsdl.org/nsdl_dc_v1.02/ http://ns.nsdl.org/schemas/nsdl_dc/nsdl_dc_v1.02.xsd</xsl:attribute> + --> + <!--no work in Java 1.5 + <xsl:attribute name="dct" namespace="http://purl.org/dc/terms/"/> + <xsl:attribute name="dc" namespace="http://purl.org/dc/elements/1.1/"/> + <xsl:attribute name="ieee" namespace="http://www.ieee.org/xsd/LOMv1p0"/> + --> + + <!--so replace root element with a text instruction; also had to exclude namespace above --> + <xsl:text disable-output-escaping="yes"><nsdl_dc:nsdl_dc schemaVersion="1.02.010" xmlns:nsdl_dc="http://ns.nsdl.org/nsdl_dc_v1.02/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dct="http://purl.org/dc/terms/" xmlns:ieee="http://www.ieee.org/xsd/LOMv1p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ns.nsdl.org/nsdl_dc_v1.02/ http://ns.nsdl.org/schemas/nsdl_dc/nsdl_dc_v1.02.xsd"></xsl:text> + <xsl:value-of select="$newline"/> + <!--dc:title--> *************** *** 1750,1754 **** <!--end nsdl:dc--> ! </xsl:element> </xsl:template> --- 1772,1778 ---- <!--end nsdl:dc--> ! <!-- </xsl:element>--> ! <xsl:value-of select="$newline"/> ! <xsl:text disable-output-escaping="yes"></nsdl_dc:nsdl_dc></xsl:text> </xsl:template> |
|
From: John W. <jwe...@us...> - 2007-01-18 22:46:19
|
Update of /cvsroot/dlese/oai-project/web/WEB-INF In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv2188/web/WEB-INF Modified Files: web.xml Log Message: fixed the adn to nsdl_dc transform with ASN identifiers to work with the default Java 1.5 XSLT processor Index: web.xml =================================================================== RCS file: /cvsroot/dlese/oai-project/web/WEB-INF/web.xml,v retrieving revision 1.66 retrieving revision 1.67 diff -C2 -r1.66 -r1.67 *** web.xml 17 Jan 2007 19:42:50 -0000 1.66 --- web.xml 18 Jan 2007 22:46:16 -0000 1.67 *************** *** 6,11 **** <!-- web.xml setup for the jOAI application --> ! <web-app> ! <display-name>jOAI (v@VERSION@)</display-name> --- 6,10 ---- <!-- web.xml setup for the jOAI application --> ! <web-app> <display-name>jOAI (v@VERSION@)</display-name> *************** *** 120,132 **** must begin with the string 'xslconverter' and must be unique. The param-value must be of the form 'xslfile.xsl|[from format]|[to format]'. ! The XSL file must be placed in the directory WEB-INF/xsl_files/. --> ! <context-param> ! <param-name>xslconverter - adn to oai_dc converter</param-name> ! <param-value>adn-v0.6.50-to-oai_dc.xsl|adn|oai_dc</param-value> ! </context-param> ! <context-param> ! <param-name>xslconverter - adn to nsdl_dc converter</param-name> ! <param-value>adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl|adn|nsdl_dc</param-value> ! </context-param> <context-param> <param-name>xslconverter - adn to briefmeta converter</param-name> --- 119,123 ---- must begin with the string 'xslconverter' and must be unique. The param-value must be of the form 'xslfile.xsl|[from format]|[to format]'. ! The XSL file must be placed in the directory WEB-INF/xsl_files/. --> <context-param> <param-name>xslconverter - adn to briefmeta converter</param-name> *************** *** 148,152 **** <param-name>xslconverter - dlese_anno (v0.1 or v1.0) to oai_dc converter</param-name> <param-value>dlese_anno-v1.0.00-and-v0.1.01-to-oai_dc.xsl|dlese_anno|oai_dc</param-value> ! </context-param> <!-- To configure a format converter that uses a Java class, the param-name must begin with --- 139,152 ---- <param-name>xslconverter - dlese_anno (v0.1 or v1.0) to oai_dc converter</param-name> <param-value>dlese_anno-v1.0.00-and-v0.1.01-to-oai_dc.xsl|dlese_anno|oai_dc</param-value> ! </context-param> ! <context-param> ! <param-name>xslconverter - adn to oai_dc converter</param-name> ! <param-value>adn-v0.6.50-to-oai_dc.xsl|adn|oai_dc</param-value> ! </context-param> ! <context-param> ! <param-name>xslconverter - adn to nsdl_dc converter</param-name> ! <param-value>adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl|adn|nsdl_dc</param-value> ! </context-param> ! <!-- To configure a format converter that uses a Java class, the param-name must begin with *************** *** 156,165 **** and be placed in the class path for this servlet --> ! <!-- The following two crosswalk handlers have been replaced by xsl converters --> <!-- <context-param> <param-name>javaconverter - Converts from adn to the NSDL DC format</param-name> <param-value>org.dlese.dpc.xml.ADNToNSDLDCFormatConverter|adn|nsdl_dc</param-value> ! </context-param> --> ! <!-- <context-param> <param-name>javaconverter - Converts from adn to the OAI DC format</param-name> <param-value>org.dlese.dpc.xml.ADNToOAIDCFormatConverter|adn|oai_dc</param-value> --- 156,167 ---- and be placed in the class path for this servlet --> ! <!-- The following two crosswalk handlers are alternatives to the above xsl converters for ! adn to nsdl_dc and oai_dc. Note that the adn to nsdl_dc java converter hangs with the ! asn identifier version of the crosswalk --> <!-- <context-param> <param-name>javaconverter - Converts from adn to the NSDL DC format</param-name> <param-value>org.dlese.dpc.xml.ADNToNSDLDCFormatConverter|adn|nsdl_dc</param-value> ! </context-param> ! <context-param> <param-name>javaconverter - Converts from adn to the OAI DC format</param-name> <param-value>org.dlese.dpc.xml.ADNToOAIDCFormatConverter|adn|oai_dc</param-value> *************** *** 167,171 **** ! <!-- ***************** Params used by the Java XML converters above (no longer used) ****************** --> <context-param> --- 169,173 ---- ! <!-- ***************** Params used by the Java two XML converters above ****************** --> <context-param> *************** *** 175,180 **** <context-param> <param-name>adn-to-nsdl-dc-xsl</param-name> ! <param-value>adn-v0.6.50-to-nsdl_dc-v1.02.xsl</param-value> ! <!-- <param-value>adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl</param-value> --> </context-param> <context-param> --- 177,182 ---- <context-param> <param-name>adn-to-nsdl-dc-xsl</param-name> ! <param-value>adn-v0.6.50-to-nsdl_dc-v1.02-asn-identifiers.xsl</param-value> ! <!-- <param-value>adn-v0.6.50-to-nsdl_dc-v1.02.xsl</param-value> --> </context-param> <context-param> |
|
From: John W. <jwe...@us...> - 2007-01-17 19:47:14
|
Update of /cvsroot/dlese/oai-project/web/docs In directory sc8-pr-cvs12.sourceforge.net:/tmp/cvs-serv23708/web/docs Modified Files: faq.jsp Log Message: updated docs Index: faq.jsp =================================================================== RCS file: /cvsroot/dlese/oai-project/web/docs/faq.jsp,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -r1.1 -r1.2 *** faq.jsp 16 Jan 2007 03:15:40 -0000 1.1 --- faq.jsp 17 Jan 2007 19:47:05 -0000 1.2 *************** *** 1,201 **** ! <%@ page contentType="text/html; charset=UTF-8" %> ! <%@ include file="../TagLibIncludes.jsp" %> ! <%@ include file="../baseUrl.jsp" %> ! <c:set var="rm" value="${applicationScope.repositoryManager}"/> ! ! <html> ! ! <head> ! <title>Frequently Asked Questions (FAQ)</title> ! <c:import url="../head.jsp"/> ! <style type="text/css"> ! <!-- ! .code {font-family: "Courier New", Courier, mono} ! --> ! </style> ! </head> ! ! <body> ! <a name="top"></a><c:import url="../top.jsp?sec=doc"/> ! <!-- content begins--> ! <h1>Frequently Asked Questions (FAQ)</h1> ! <p>This FAQ includes the following sections: </p> ! <table border="0" align="left" cellpadding="0" cellspacing="0"> ! <tr> ! <td align="left"><a href="faq.jsp#provider"> Provider FAQ</a></td> ! </tr> ! <tr> ! <td align="left"><a href="faq.jsp#harvester">Harvester FAQ</a></td> ! </tr> ! <tr> ! <td align="left"><a href="faq.jsp#general">General FAQ</a></td> ! </tr> ! </table> ! <p> </p> ! <p> </p> ! <p> </p> ! <h3><a name="provider" id="provider"></a>Provider FAQ</h3> ! <p><strong>What is different between the 'Search' and 'Admin search' pages?</strong></p> ! <p>The <a href="<c:url value='/search.jsp'/>">Search</a> page provides search ! over the full text found in all files that can be disseminated in oai_dc format. ! This includes files that reside natively in oai_dc format as well as files that ! can be converted to oai_dc as described above in <a href="<c:url value='/docs/provider.jsp#convertors'/>">Providing ! files in multiple formats</a>. In addition, only files that are enabled in the ! <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> ! page are available for search. The Search page is meant to be the public front ! for the data provider and can customized and easily installed to another location ! or remote Web server as described in the <a href="<c:url value='/docs/odlsearch.do'/>">ODL ! Search Specification</a> page. </p> ! <p>The <a href="<c:url value='/admin/query.do'/>">Admin search</a> page provides ! search over the full text found in all XML files that are configured in the ! data provider. Files are searchable and viewable even when public access to ! them has been disabled in the <a href="<c:url value='/admin/data-provider.do'/>">Metadata ! Files Configuration</a> page. Admin search also provides options to search by ! set, available format, and record attribute (not deleted, deleted, etc.). The ! Admin search page resides in the administration portion of the software and ! its access can therefore be restricted to trusted users as described in the ! <a href="<c:url value='/docs/configuring_joai.jsp'/>">Configuring jOAI</a> page. ! </p> ! <p><strong>If my records reside in a database, can I use jOAI to implement an OAI data provider for my repository?</strong></p> ! <p>The jOAI data provider allows XML files from a file system to be exposed as items in an OAI data repository. To expose records that reside in a database, write a routine to export the records to XML files at regular intervals such as once a day or once a week, depending on how often the records change. Then <a href="<c:url value='/docs/provider.jsp#provsetup'/>">setup the data provider</a> to monitor the directory or directories where the files are exported to. See also <a href="<c:url value='/docs/provider.jsp#directories'/>">preparing files for serving</a>.</p> ! <p>After the initial set of records have been exported from the database, files should be modified or deleted only when the corresponding database record has been updated or deleted. jOAI will monitor the files and provide them to harvesters according to the OAI-PMH.</p> ! <p><strong>Does jOAI support selective or incremental harvesting?</strong></p> ! <p>Yes. After performing an initial full harvest of the repository, harvesters may use <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Datestamp">datestamps</a> to request only those records that have changed or been deleted since that last time of harvest, which can greatly reduce the number of records transferred over the network over time. The data provider implements deleted records and datestamps in accordance with the OAI-PMH to support selective and incremental harvests.</p> ! <p><strong>If I remove a file, can I add it back at a later time?</strong></p> ! <p>When a file is removed from a directory that is being monitored by the data ! provider, it's record will be changed to status deleted, and harvesters will ! be notified that the record has been deleted the next time they harvest from ! the data provider. At a later time, if a file is added back with the same unique ! ID as a deleted record (regardless of the directory), the data provider will ! replace it with the new one, and it's status will no longer be deleted. Harvesters ! will then receive the new record the next time they harvest from the data provider. ! </p> ! <p><strong>What happens if I accidentally create two files with the same ID?</strong></p> ! <p>When jOAI imports a new or modified file into it's index, a check is performed to see if there is an existing record with the same unique ID. If the ID already exists, an error will be reported under 'Indexing Errors' in the the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> page, and the file will not be imported into the repository index. To fix the problem the file must either be removed from the directory or a unique ID should be assigned to the file, as described above under <a href="<c:url value='/docs/provider.jsp#directories'/>">preparing files for serving</a>.</p> ! <p><strong>My records have indexing errors when I put them in the data provider. What's wrong?</strong></p> ! <p> XML files that contain text that was copied and pasted from tools such as Microsoft Word often contain invalid characters such as dashes or copyright symbols that are improperly encoded. These 'bad characters' can trigger the XML processors in the software to issue an error. Files must contain well-formed XML and should use UTF-8 encoding. Character references, rather than entity references, should also be used for special characters, as required by the OAI protocol <a href="http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse">XML response format</a>.</p> ! <p><strong>How many records can the data provider scale to?</strong></p> ! <p>The jOAI data provider is designed for small to medium size data repositories. ! The software has been tested successfully with repositories up to 300,000 records. ! The number of records the software can support depends on the amount of memory ! available to the Java JVM, the speed of the host machine and the size of the ! individual records in the repository.</p> ! <p><strong>The baseURL that is shown uses the local machine name, but it should use the domain name for the server instead. How can I change it?</strong></p> ! <p>The base URL that is shown on the <a href="<c:url value='/'/>">front page</a> ! and <a href="<c:url value='/admin/data-provider-info.do'/>">Repository Information ! page</a> of jOAI and elsewhere reflects the URL that was entered into the web ! browser when connecting to the software. For example, if a user accesses jOAI ! using the web address http://localhost:8080${pageContext.request.contextPath}, ! the baseURL will be shown as 'http://localhost:8080${pageContext.request.contextPath}/${initParam.dataProviderBaseUrlPathEnding}'. ! If the user connects to the same instance of jOAI using the Internet address ! http://myserver.somewhere.edu${pageContext.request.contextPath}, the baseURL ! will be shown as 'http://myserver.somewhere.edu${pageContext.request.contextPath}/${initParam.dataProviderBaseUrlPathEnding}'. ! </p> ! <p><strong>Can I see who has harvested from the data provider?</strong></p> ! <p>Yes. To see a list of who has harvested from the data provider, go to the <a href="<c:url value='/admin/provider_status_setup.jsp'/>">Provider ! Setup and Status</a> page and see the 'Reports' section for a link to the harvest ! history. The report lists all harvest ListRecords activity that resulted in ! one or more records being transferred.</p> ! <p> </p> ! <p><a href="faq.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="harvester" id="harvester"></a>Harvester FAQ</h3> ! <p><strong>Where are the harvested records and zip archives saved to?</strong></p> ! <p>The harvester saves the records that are harvested into individual files on ! the file system, one record per file. Files are saved to either a default directory ! (which is named based upon the name of the provider and optionally the set that ! is being harvested) or a specific directory that was specified when <a href="<c:url value='/docs/harvester.jsp#how'/>">setting ! up</a> the harvest. Each harvest is then packaged into a zip archive. </p> ! <p> To determine where files and zip archives were saved to after a harvest has ! occurred, go to the <a href="<c:url value='/admin/harvester.do'/>">Harvester ! Setup and Status</a> page, then click on 'View harvest history' for a given ! harvest. This brings up the detailed history of harvests and shows the full ! directory path to the harvested files and zip archives.</p> ! <p>Each time a harvest is performed for a given harvest configuration, files in ! the harvest directory may be added, updated or deleted by the harvester depending ! on the outcome of the harvest. At the conclusion of each harvest that results ! in a change to one or more files, a new zip archive is created, and a maximum ! of three zip archives are preserved at any given time. Each zip archive contains ! the exact time of the harvest in its name. The zip archives for each harvest ! may be downloaded directly from the <a href="<c:url value='/admin/harvester.do'/>">Harvester ! Setup and Status</a> page or accessed from the file system. </p> ! <p><strong>Can I use jOAI to harvest records into a database?</strong></p> ! <p>There are two ways in which the harvester may be used to import records into ! a database.</p> ! <p>The first method, which uses the jOAI web application, requires two parts. ! First, configure the jOAI harvester to save files to a convenient directory ! at regular intervals, such as once a day. Then, write a routine to monitor the ! file directory and add, update or delete the corresponding records to the database ! when changes occur in the files. </p> ! <p>Another method is to use the <a href="<c:url value='/docs/javadoc/org/dlese/dpc/oai/harvester/Harvester.html'/>">Harvester ! API</a> from within native Java code to perform harvests and import metadata ! records directly into a database.</p> ! <p><strong>Does the harvester support selective or incremental harvesting?</strong></p> ! <p>Yes. When an automatic harvest is conducted at regular intervals, the harvester ! checks if the data provider supports deleted records. If deletions are supported, ! a <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Datestamp">selective ! harvest</a> is performed by requesting and synchronizing only those records ! that have been added, modified or deleted since the previous harvest. If deletions ! are not supported, a full harvest is performed by deleting all previously harvested ! records and harvesting all records from scratch.</p> ! <p>Similarly when a manual harvest is performed, clicking 'New' performs a selective ! harvest while clicking 'All' deletes all previously harvested files and performs ! a full harvest from scratch.</p> ! <p><strong>The files that are saved by the harvester include characters like '%3A' ! in their names. Why is that?</strong></p> ! <p>When the harvester saves records, it places each record in a single file, which ! is named using the OAI identifier associated with the record that was harvested. ! Reserved characters such as the colon ':' are encoded using hexadecimal values ! in order to ensure the file name is valid on the file system. For example, if ! the OAI identifier for a given harvested record is oai:dlese.org:123-ABC, the ! file will be named oai%3Adlese.org%3A123-ABC.xml. The hexadecimal characters ! can be converted back to the original form as needed. </p> ! <p><strong>How can I provide records that I harvest?</strong></p> ! <p>Currently it is a two step process to make records that are harvested available ! through the data provider. First, harvest the records to a convenient file directory. ! Second, configure the data provider to point to the same file directory. As ! new records are added, modified or deleted by the harvester, these changes will ! be reflected and passed along in the data provider.</p> ! <p><strong>Can I search over and view the records I harvest?</strong></p> ! <p>The harvester portion of the software does not currently support searching ! and viewing harvested records directly. However, by configuring harvested records ! in the data provider as mentioned above, the records will become searchable ! and viewable in the 'Search' and 'Admin Search' pages.</p> ! <p> </p> ! <p><a href="faq.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="general" id="general"></a>General FAQ</h3> ! <p><strong>Can jOAI be configured to run through an Apache web server (httpd)?</strong></p> ! <p>Yes. Running jOAI through an <a href="http://httpd.apache.org/">Apache web ! server</a> provides additional functionality that is not available through <a href="http://tomcat.apache.org/">Tomcat</a> ! alone. For example, Apache provides robust support for SSL, user authorization ! and authentication, access control by IP address, virtual host support, web ! logging, URL redirection, and other functionality. By configuring Tomcat to ! run through Apache, all of Apache's functionality becomes available. This may ! be especially convenient for web administrators who are already familiar with ! Apache.</p> ! <p>To configure jOAI to run with Apache, use the <a href="http://tomcat.apache.org/connectors-doc/" >Apache ! Tomcat Connector</a> (mod_jk) in conjunction with Tomcat. The connector allows ! rules to be defined that say, for example, 'for all requests that come to Apache ! at the web address http://oai.somewhere.edu, forward them to Tomcat installed ! at http://www.somewhere.edu:8080/oai/'. Information for setting up mod_jk is ! provided in the <a href="http://tomcat.apache.org/connectors-doc/">Apache Tomcat ! Connector documentation</a>. </p> ! <p>A typical configuration scenario would be to use Apache to provide SSL encryption, ! user authorization and authentication for all pages that reside in the admin ! area of the software (e.g. https://oai.somewhere.edu/oai/admin*), while leaving ! all other public jOAI pages open. This scenario provides a relatively secure ! way to restrict access to the administrative functions of the software to trusted ! users while leaving access to the data provider, search and other public pages ! open. </p> ! <p>Another scenario might be to restrict access to the software or portions of ! the software by requestors IP address.</p> ! <p>See the <a href="http://httpd.apache.org/docs/">Apache documentation</a> for ! a list of available features and configuration information.</p> ! <p> </p> ! <p><a href="faq.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <c:import url="../bottom.jsp"/> ! </body> ! </html> ! --- 1,201 ---- ! <%@ page contentType="text/html; charset=UTF-8" %> ! <%@ include file="../TagLibIncludes.jsp" %> ! <%@ include file="../baseUrl.jsp" %> ! <c:set var="rm" value="${applicationScope.repositoryManager}"/> ! ! <html> ! ! <head> ! <title>Frequently Asked Questions (FAQ)</title> ! <c:import url="../head.jsp"/> ! <style type="text/css"> ! <!-- ! .code {font-family: "Courier New", Courier, mono} ! --> ! </style> ! </head> ! ! <body> ! <a name="top"></a><c:import url="../top.jsp?sec=doc"/> ! <!-- content begins--> ! <h1>Frequently Asked Questions (FAQ)</h1> ! <p>This FAQ includes the following sections: </p> ! <table border="0" align="left" cellpadding="0" cellspacing="0"> ! <tr> ! <td align="left"><a href="faq.jsp#provider"> Provider FAQ</a></td> ! </tr> ! <tr> ! <td align="left"><a href="faq.jsp#harvester">Harvester FAQ</a></td> ! </tr> ! <tr> ! <td align="left"><a href="faq.jsp#general">General FAQ</a></td> ! </tr> ! </table> ! <p> </p> ! <p> </p> ! <p> </p> ! <h3><a name="provider" id="provider"></a>Provider FAQ</h3> ! <p><strong>What is different between the 'Search' and 'Admin search' pages?</strong></p> ! <p>The <a href="<c:url value='/search.jsp'/>">Search</a> page provides search ! over the full text found in all files that can be disseminated in oai_dc format. ! This includes files that reside natively in oai_dc format as well as files that ! can be converted to oai_dc as described in <a href="<c:url value='/docs/provider.jsp#convertors'/>">Providing ! files in multiple formats</a>. In addition, only files that are enabled in the ! <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> ! page are available for search. The Search page is meant to be the public front ! for the data provider and can customized and easily installed to another location ! or remote Web server as described in the <a href="<c:url value='/docs/odlsearch.do'/>">ODL ! Search Specification</a> page. </p> ! <p>The <a href="<c:url value='/admin/query.do'/>">Admin search</a> page provides ! search over the full text found in all XML files that are configured in the ! data provider. Files are searchable and viewable even when public access to ! them has been disabled in the <a href="<c:url value='/admin/data-provider.do'/>">Metadata ! Files Configuration</a> page. Admin search also provides options to search by ! set, available format, and record attribute (not deleted, deleted, etc.). The ! Admin search page resides in the administration portion of the software and ! its access can therefore be restricted to trusted users as described in the ! <a href="<c:url value='/docs/configuring_joai.jsp'/>">Configuring jOAI</a> page. ! </p> ! <p><strong>If my records reside in a database, can I use jOAI to implement an OAI data provider for my repository?</strong></p> ! <p>The jOAI data provider allows XML files from a file system to be exposed as items in an OAI data repository. To expose records that reside in a database, write a routine to export the records to XML files at regular intervals such as once a day or once a week, depending on how often the records change. Then <a href="<c:url value='/docs/provider.jsp#provsetup'/>">setup the data provider</a> to monitor the directory or directories where the files are exported to. See also <a href="<c:url value='/docs/provider.jsp#directories'/>">preparing files for serving</a>.</p> ! <p>After the initial set of records have been exported from the database, files should be modified or deleted only when the corresponding database record has been updated or deleted. jOAI will monitor the files and provide them to harvesters according to the OAI-PMH.</p> ! <p><strong>Does jOAI support selective or incremental harvesting?</strong></p> ! <p>Yes. After performing an initial full harvest of the repository, harvesters may use <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Datestamp">datestamps</a> to request only those records that have changed or been deleted since that last time of harvest, which can greatly reduce the number of records transferred over the network over time. The data provider implements deleted records and datestamps in accordance with the OAI-PMH to support selective and incremental harvests.</p> ! <p><strong>If I remove a file, can I add it back at a later time?</strong></p> ! <p>When a file is removed from a directory that is being monitored by the data ! provider, it's record will be changed to status deleted, and harvesters will ! be notified that the record has been deleted the next time they harvest from ! the data provider. At a later time, if a file is added back with the same unique ! ID as a deleted record (regardless of the directory), the data provider will ! replace it with the new one, and it's status will no longer be deleted. Harvesters ! will then receive the new record the next time they harvest from the data provider. ! </p> ! <p><strong>What happens if I accidentally create two files with the same ID?</strong></p> ! <p>When jOAI imports a new or modified file into it's index, a check is performed to see if there is an existing record with the same unique ID. If the ID already exists, an error will be reported under 'Indexing Errors' in the the <a href="<c:url value='/admin/data-provider.do'/>">Metadata Files Configuration</a> page, and the file will not be imported into the repository index. To fix the problem the file must either be removed from the directory or a unique ID should be assigned to the file, as described under <a href="<c:url value='/docs/provider.jsp#directories'/>">preparing files for serving</a>.</p> ! <p><strong>My records have indexing errors when I put them in the data provider. What's wrong?</strong></p> ! <p> XML files that contain text that was copied and pasted from tools such as Microsoft Word often contain invalid characters such as dashes or copyright symbols that are improperly encoded. These 'bad characters' can trigger the XML processors in the software to issue an error. Files must contain well-formed XML and should use UTF-8 encoding. Character references, rather than entity references, should also be used for special characters, as required by the OAI protocol <a href="http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse">XML response format</a>.</p> ! <p><strong>How many records can the data provider scale to?</strong></p> ! <p>The jOAI data provider is designed for small to medium size data repositories. ! The software has been tested successfully with repositories up to 300,000 records. ! The number of records the software can support depends on the amount of memory ! available to the Java JVM, the speed of the host machine and the size of the ! individual records in the repository.</p> ! <p><strong>The baseURL that is shown uses the local machine name, but it should use the domain name for the server instead. How can I change it?</strong></p> ! <p>The base URL that is shown on the <a href="<c:url value='/'/>">front page</a> ! and <a href="<c:url value='/admin/data-provider-info.do'/>">Repository Information ! page</a> of jOAI and elsewhere reflects the URL that was entered into the web ! browser when connecting to the software. For example, if a user accesses jOAI ! using the web address http://localhost:8080${pageContext.request.contextPath}, ! the baseURL will be shown as 'http://localhost:8080${pageContext.request.contextPath}/${initParam.dataProviderBaseUrlPathEnding}'. ! If the user connects to the same instance of jOAI using the Internet address ! http://myserver.somewhere.edu${pageContext.request.contextPath}, the baseURL ! will be shown as 'http://myserver.somewhere.edu${pageContext.request.contextPath}/${initParam.dataProviderBaseUrlPathEnding}'. ! </p> ! <p><strong>Can I see who has harvested from the data provider?</strong></p> ! <p>Yes. To see a list of who has harvested from the data provider, go to the <a href="<c:url value='/admin/provider_status_setup.jsp'/>">Provider ! Setup and Status</a> page and see the 'Reports' section for a link to the harvest ! history. The report lists all harvest ListRecords activity that resulted in ! one or more records being transferred.</p> ! <p> </p> ! <p><a href="faq.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="harvester" id="harvester"></a>Harvester FAQ</h3> ! <p><strong>Where are the harvested records and zip archives saved to?</strong></p> ! <p>The harvester saves the records that are harvested into individual files on ! the file system, one record per file. Files are saved to either a default directory ! (which is named based upon the name of the provider and optionally the set that ! is being harvested) or a specific directory that was specified when <a href="<c:url value='/docs/harvester.jsp#how'/>">setting ! up</a> the harvest. Each harvest is then packaged into a zip archive. </p> ! <p> To determine where files and zip archives were saved to after a harvest has ! occurred, go to the <a href="<c:url value='/admin/harvester.do'/>">Harvester ! Setup and Status</a> page, then click on 'View harvest history' for a given ! harvest. This brings up the detailed history of harvests and shows the full ! directory path to the harvested files and zip archives.</p> ! <p>Each time a harvest is performed for a given harvest configuration, files in ! the harvest directory may be added, updated or deleted by the harvester depending ! on the outcome of the harvest. At the conclusion of each harvest that results ! in a change to one or more files, a new zip archive is created, and a maximum ! of three zip archives are preserved at any given time. Each zip archive contains ! the exact time of the harvest in its name. The zip archives for each harvest ! may be downloaded directly from the <a href="<c:url value='/admin/harvester.do'/>">Harvester ! Setup and Status</a> page or accessed from the file system. </p> ! <p><strong>Can I use jOAI to harvest records into a database?</strong></p> ! <p>There are two ways in which the harvester may be used to import records into ! a database.</p> ! <p>The first method, which uses the jOAI web application, requires two parts. ! First, configure the jOAI harvester to save files to a convenient directory ! at regular intervals, such as once a day. Then, write a routine to monitor the ! file directory and add, update or delete the corresponding records to the database ! when changes occur in the files. </p> ! <p>Another method is to use the <a href="<c:url value='/docs/javadoc/org/dlese/dpc/oai/harvester/Harvester.html'/>">Harvester ! API</a> from within native Java code to perform harvests and import metadata ! records directly into a database.</p> ! <p><strong>Does the harvester support selective or incremental harvesting?</strong></p> ! <p>Yes. When an automatic harvest is conducted at regular intervals, the harvester ! checks if the data provider supports deleted records. If deletions are supported, ! a <a href="http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Datestamp">selective ! harvest</a> is performed by requesting and synchronizing only those records ! that have been added, modified or deleted since the previous harvest. If deletions ! are not supported, a full harvest is performed by deleting all previously harvested ! records and harvesting all records from scratch.</p> ! <p>Similarly when a manual harvest is performed, clicking 'New' performs a selective ! harvest while clicking 'All' deletes all previously harvested files and performs ! a full harvest from scratch.</p> ! <p><strong>The files that are saved by the harvester include characters like '%3A' ! in their names. Why is that?</strong></p> ! <p>When the harvester saves records, it places each record in a single file, which ! is named using the OAI identifier associated with the record that was harvested. ! Reserved characters such as the colon ':' are encoded using hexadecimal values ! in order to ensure the file name is valid on the file system. For example, if ! the OAI identifier for a given harvested record is oai:dlese.org:123-ABC, the ! file will be named oai%3Adlese.org%3A123-ABC.xml. The hexadecimal characters ! can be converted back to the original form as needed. </p> ! <p><strong>How can I provide records that I harvest?</strong></p> ! <p>Currently it is a two step process to make records that are harvested available ! through the data provider. First, harvest the records to a convenient file directory. ! Second, configure the data provider to point to the same file directory. As ! new records are added, modified or deleted by the harvester, these changes will ! be reflected and passed along in the data provider.</p> ! <p><strong>Can I search over and view the records I harvest?</strong></p> ! <p>The harvester portion of the software does not currently support searching ! and viewing harvested records directly. However, by configuring harvested records ! in the data provider as mentioned above, the records will become searchable ! and viewable in the 'Search' and 'Admin Search' pages.</p> ! <p> </p> ! <p><a href="faq.jsp#top"> <img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <h3><a name="general" id="general"></a>General FAQ</h3> ! <p><strong>Can jOAI be configured to run through an Apache web server (httpd)?</strong></p> ! <p>Yes. Running jOAI through an <a href="http://httpd.apache.org/">Apache web ! server</a> provides additional functionality that is not available through <a href="http://tomcat.apache.org/">Tomcat</a> ! alone. For example, Apache provides robust support for SSL, user authorization ! and authentication, access control by IP address, virtual host support, web ! logging, URL redirection, and other functionality. By configuring Tomcat to ! run through Apache, all of Apache's functionality becomes available. This may ! be especially convenient for web administrators who are already familiar with ! Apache.</p> ! <p>To configure jOAI to run with Apache, use the <a href="http://tomcat.apache.org/connectors-doc/" >Apache ! Tomcat Connector</a> (mod_jk) in conjunction with Tomcat. The connector allows ! rules to be defined that say, for example, 'for all requests that come to Apache ! at the web address http://oai.somewhere.edu, forward them to Tomcat installed ! at http://www.somewhere.edu:8080/oai/'. Information for setting up mod_jk is ! provided in the <a href="http://tomcat.apache.org/connectors-doc/">Apache Tomcat ! Connector documentation</a>. </p> ! <p>A typical configuration scenario would be to use Apache to provide SSL encryption, ! user authorization and authentication for all pages that reside in the admin ! area of the software (e.g. https://oai.somewhere.edu/oai/admin*), while leaving ! all other public jOAI pages open. This scenario provides a relatively secure ! way to restrict access to the administrative functions of the software to trusted ! users while leaving access to the data provider, search and other public pages ! open. </p> ! <p>Another scenario might be to restrict access to the software or portions of ! the software by requestors IP address.</p> ! <p>See the <a href="http://httpd.apache.org/docs/">Apache documentation</a> for ! a list of available features and configuration information.</p> ! <p> </p> ! <p><a href="faq.jsp#top"><img src="<c:url value='/images/arrowup.gif'/>" alt="top" width="9" height="11" border="0" title="back to top"></a></p> ! <hr> ! <c:import url="../bottom.jsp"/> ! </body> ! </html> ! |