- Updated to OpenACS 5.9.1

acs-reference.info

@@ -7,10 +7,10 @@
     <initial-install-p>t</initial-install-p>
     <singleton-p>t</singleton-p>
 
-    <version name="5.9.0" url="http://openacs.org/repository/download/apm/acs-reference-5.9.0.apm">
+    <version name="5.9.1" url="http://openacs.org/repository/download/apm/acs-reference-5.9.1.apm">
         <owner url="mailto:jon@jongriffin.com">Jon Griffin</owner>
-        <summary>Tools and API for managing refrence data.</summary>
-        <release-date>2015-10-04</release-date>
+        <summary>Tools and API for managing reference data.</summary>
+        <release-date>2017-08-06</release-date>
         <maturity>3</maturity>
         <vendor url="http://www.mayuli.com">Mayuli Enterprises, LLC</vendor>
 	<license url="http://www.gnu.org/copyleft/gpl.html">GPL</license>
@@ -20,8 +20,8 @@
 &lt;li&gt; Running standard reports on this data.
 &lt;li&gt; Monitoring the usage of reference data.
 &lt;/ul&gt;</description>
-        <provides url="acs-reference" version="5.9.0"/>
-        <requires url="acs-kernel" version="5.9.0"/>
+        <provides url="acs-reference" version="5.9.1"/>
+        <requires url="acs-kernel" version="5.9.1"/>
 
         <callbacks>
         </callbacks>

www/doc/index.adp

@@ -7,8 +7,6 @@
 <ul>
 <li><a href="requirements">Requirements</a></li><li><a href="design">Design</a></li>
 </ul>
-<p>Current docs are always at:<br><a href="http://www.jongriffin.com/static/openacs">jongriffin.com</a>
-</p>
 <h2>Release Notes</h2>
 <p>Please file bugs in the <a href="http://openacs.org/bugtracker/openacs/">Bug Tracker</a>.</p>
 <hr>

www/doc/index.html

@@ -10,9 +10,6 @@
 <li><a href="requirements.html">Requirements</a></li>
 <li><a href="design.html">Design</a></li>
 </ul>
-<p>Current docs are always at:<br>
-<a href="http://www.jongriffin.com/static/openacs">jongriffin.com</a>
-</p>
 <h2>Release Notes</h2>
 
 <p>Please file bugs in the <a href="http://openacs.org/bugtracker/openacs/">Bug Tracker</a>.</p>

www/doc/requirements.adp

@@ -17,11 +17,11 @@ this data.</li><li>It offers a convenient repository for and the ability to run
 reports on data of this sort.</li><li>It allows us to monitor the usage of reference data.</li>
 </ul>
 <h3>II. Vision Statement</h3>
-<p>What is reference data? Simply put, it is data that doesn't
+<p>What is reference data? Simply put, it is data that doesn&#39;t
 change very often and also in many cases comes from an external
 source and not from within the system itself. Many times it is
-created from a standards body, i.e. <a href="http://www.iso.ch/">ISO</a> or <a href="http://www.ansi.org">ANSI</a>, and may be required for a client's
-particular industrial needs.</p>
+created from a standards body, i.e. <a href="http://www.iso.ch/">ISO</a> or <a href="http://www.ansi.org">ANSI</a>, and may be required for a
+client&#39;s particular industrial needs.</p>
 <p>Some examples of reference data are:</p>
 <ul>
 <li>Geographic data: zip codes, country codes and
@@ -34,7 +34,7 @@ so most data models simply defer the issue by treating reference
 data as something simple to implement. Elsewhere. The reality is
 that for most organizations reference data is extremely important
 and also extremely difficult to manage.</p>
-<p>This module will not only <i>package</i> all of a site's
+<p>This module will not only <em>package</em> all of a site&#39;s
 reference data in one place, it will also help manage that
 data.</p>
 <h3>III. System Overview</h3>
@@ -55,7 +55,7 @@ information for him.</p>
 <h3>V. Related Links</h3>
 <ul><li><a href="design">Design document</a></li></ul>
 <h3>VI.A Requirements: Data Model</h3>
-<p>10.10 The package should use a table that is the <i>master</i>
+<p>10.10 The package should use a table that is the <em>master</em>
 table for all reference tables.<br>
 10.20 The package should employ a field to show whether this data
 is internally derived or not.<br>
@@ -79,15 +79,15 @@ particular table has expired.</p>
 <p>The requirements below are not met by the current
 implementation:</p>
 <p>30.10 There needs to be a way to query the data source and
-update automatically. If that isn't possible, as it won't be in
-many cases, the application should be able to query a master server
-and see if there is new data for a particular table or tables. For
-example: refdata.arsdigita.com could hold the reference tables and
-when newer table versions become available, simply upload only
-these versions or perhaps even only the differences between the
-tables. In any case, there should be an admin page that shows
-current status and revisions of various data, where to find info
-about additional sources (if applicable), and provide a UI to
+update automatically. If that isn&#39;t possible, as it won&#39;t
+be in many cases, the application should be able to query a master
+server and see if there is new data for a particular table or
+tables. For example: refdata.arsdigita.com could hold the reference
+tables and when newer table versions become available, simply
+upload only these versions or perhaps even only the differences
+between the tables. In any case, there should be an admin page that
+shows current status and revisions of various data, where to find
+info about additional sources (if applicable), and provide a UI to
 upload or import new data.</p>
 <h3>VII. Implementation Notes</h3>
 <p>The package needs to handle changes to reference data in a
@@ -96,15 +96,15 @@ countries, what should happen?</p>
 <ul>
 <li>The reference package should note this change.</li><li>The appropriate table is updated. In this case countries et
 al.</li><li>An update to the repository database field effective_date is
-added.</li><li>A <i>diff</i> type of entry into the reference repository
-history. <font color="red"><i>This is not in the current data
-model</i></font>
+added.</li><li>A <em>diff</em> type of entry into the reference repository
+history. <font color="red"><em>This is not in the current data
+model</em></font>
 </li><li>Then any sub-programs using this data will note the change of
 effective date and be able to handle the change as needed (i.e.
-simply read the new table).</li><li>Historical data will be available using this <i>diff</i> for
+simply read the new table).</li><li>Historical data will be available using this <em>diff</em> for
 those applications that need to use the old data</li>
 </ul>
 <p>Note also that it is possible to have overlapping effective
 dates. This will not be implemented in the first version, but
-should be recognized and accomodated throughout the development
+should be recognized and accommodated throughout the development
 process for the service package.</p>

www/doc/requirements.html

@@ -109,7 +109,7 @@ fashion. For example, if a country splits into two or more countries, what shoul
 <li>Historical data will be available using this <i>diff</i> for those applications that need to use the old data</li>
 </ul>
 <p>Note also that it is possible to have overlapping effective dates. 
-This will not be implemented in the first version, but should be recognized and accomodated throughout the development
+This will not be implemented in the first version, but should be recognized and accommodated throughout the development
 process for the service package.  
 </p>
 

www/reference-data-list.adp

@@ -3,7 +3,7 @@
 <property name="doc(title)">@title;literal@</property>
 
 <if @data:rowcount@ eq 0>
-<i>You have no reference data in the database right now.</i><p>
+<em>You have no reference data in the database right now.</em><p>
 </if>
 
 <else>

www/reference-data-list.tcl

@@ -19,8 +19,7 @@ set context_bar [list "$title"]
  
 set user_id [ad_conn user_id]
 
-db_multirow data data_select { 
-}
+db_multirow data data_select {}
 
 ad_return_template
 # Local variables:

www/view-one-reference.tcl

@@ -19,7 +19,7 @@ set title "View one Table"
 set context_bar [list [list "reference-list" "Reference List" ] "$title"]
 set user_id [ad_conn user_id]
 
-db_1row get_table { *SQL* } -column_array table_info
+db_1row get_table {} -column_array table_info
 
 ad_return_template