1,723,085 research outputs found
bety: BETYdb 4.0.1
No full text<p>This is a minor release that extends the API search syntax to the traits_and_yeidls_view and fixes some bugs in the Trait and Yield creation and update pages. It was deployed to <a href="http://www.betydb.org">www.betydb.org</a> on April 30, 2015.</p>
<a class="anchor" href="#summary-of-changes"><span class="octicon octicon-link"></span></a>Summary of Changes
<a class="anchor" href="#feature-additions"><span class="octicon octicon-link"></span></a>Feature Additions
<ul>
<li><p>It is now possible to get query results from the traits_and_yields_view SQL view using multiple columnname=value clauses in the query string appended to the Advanced Search page URLs <a href="https://www.betydb.org/search.xml">https://www.betydb.org/search.xml</a> (for results in XML format) and <a href="https://www.betydb.org/search.json">https://www.betydb.org/search.json</a> (for results in JSON format). For example, the URL <a href="https://www.betydb.org/search.xml?lat=42.9&lon=-72.3&result_type=traits">https://www.betydb.org/search.xml?lat=42.9&lon=-72.3&result_type=traits</a> will find all checked trait data for sites located at 42.9 deg N latitude and 72.3 deg W longitude to which the user has access rights and return it in XML format. Note that matches must be exact! These strict search clauses may be combined with the less-strict searching provided by a clause of the form search=term1+term2+term3... which requires only that each of the terms provided be textually included in the column value of one of the columns sitename, city, scientificname, commonname, author, trait, trait_description, or citation_year.</p></li>
<li>
<p>A new rake task has been added as a convenience for displaying the database configuration file database.yml. Run</p>
rake dbconf
</li>
</ul>
<a class="anchor" href="#bug-fixes"><span class="octicon octicon-link"></span></a>Bug Fixes
<ul>
<li><p>A long-standing bug in the processing of the New Yield and Editing Yield forms rendered the Julian date fields useless. This has been fixed.</p></li>
<li><p>In addition, the upgrade to Rails 3.2 produced some new problems with the way the standard date fields in the New Yield and Editing Yield forms were processed. Furthermore, when the New Trait and New Yield forms were visited with a row id parameter passed in the URL, the forms would be pre-populated as before, but pressing the Create button would do an update rather than creating a new row as it was supposed to. These problems have been fixed as well.</p></li>
<li><p>Finally, API queries involving an include[]=<table> clause now once again show information for the included table in the query results. Even with this, queries work slightly differently than they did prior to the update to Rails 3.2. Details will be given in the BETYdb Data Access document at <a href="https://www.authorea.com/users/5574/articles/7062">https://www.authorea.com/users/5574/articles/7062</a>.</p></li>
</ul>
<a class="anchor" href="#status-of-rspec-tests"><span class="octicon octicon-link"></span></a>Status of RSpec Tests
<ul>
<li>
<p>All tests continue to pass when run in the default environment and can be run using the command</p>
bundle exec rspec
</li>
</ul>
<p>Complete details for running the rspec tests are on the updated Wiki page at <a href="https://github.com/PecanProject/bety/wiki/Automated-Tests">https://github.com/PecanProject/bety/wiki/Automated-Tests</a></p>
Aku pergi : kumpulan tulisan Bety C. Rumkoda
No full textBuku ini merupakan kumpulan tulisan Ibu Bety C. Rumkoda tentang cerpen, cerita rakyat, puisi, dan pantun. Adapun yang terkadung di dalam tulisan ialah nilai sosial, edukasi, dan moral, dan juga kearifan lokal dari karya sastra tersebut. Semoga dengan adanya buku ini, bisa menambah khazanah buku-buku yang ada di Maluk
bety: BETYdb 4.0
No full text<p>Enhanced API for rOpensci traits package; upgrade to rails 3.2, Ruby 2.1.5. </p>
<p>This release upgrades the Rails version from Rails 3.0.18 to Rails 3.2.21 and changes the RVM-specified version of Ruby from version 1.9.3-p429 to version 2.1.5. In addition to these changes which in and of themselves make for improved security, there are numerous minor changes to the Rails code including security fixes, removal of obsolete code, fixes and improvements to the query API, and phase-out of vendor plugins in favor of gems, </p>
<a class="anchor" href="#changes-pertinent-to-pecan-users"><span class="octicon octicon-link"></span></a>Changes Pertinent to PEcAn Users
<p><strong><em>Administrators need to do a database migration.</em></strong></p>
<p>See "Database Changes" below.</p>
<a class="anchor" href="#summary-of-changes"><span class="octicon octicon-link"></span></a>Summary of Changes
<a class="anchor" href="#new-features"><span class="octicon octicon-link"></span></a>New Features
<a class="anchor" href="#enhanced-api-for-ropensci-traits-package"><span class="octicon octicon-link"></span></a>Enhanced API for rOpensci traits package
<p>See section 2 of the BETYdb Data Access guide at <a href="https://www.authorea.com/users/5574/articles/7062">https://www.authorea.com/users/5574/articles/7062</a>.</p>
<a class="anchor" href="#api-key-generation"><span class="octicon octicon-link"></span></a>API Key generation
<p>Users may now generate their own API keys by going to the Users page and clicking the "key" button. And there is now a new rake task that administrators can use to generate API keys for all current users. See section 2.3 of the BETYdb Data Access guide at <a href="https://www.authorea.com/users/5574/articles/7062">https://www.authorea.com/users/5574/articles/7062</a>.</p>
<a class="anchor" href="#directory-specific-session-keys"><span class="octicon octicon-link"></span></a>Directory-Specific Session Keys
<p>When multiple copies of BETYdb are deployed on the same host, they now use differently-named session cookies (assuming the basenames of the Rails root directories are different). This mainly affects developers who may visit different copies of BETYdb on the same host simultaneously; up to now, such users will likely have seen baffling interactions between the two copies.</p>
<a class="anchor" href="#updated-version-of-selenium-webdriver"><span class="octicon octicon-link"></span></a>Updated version of selenium-webdriver
<p>The Gem version specification for selenium-webdriver has been changed to a version compatible with the latest versions of Firefox. This mainly affects those running the RSpec tests in debug mode.</p>
<a class="anchor" href="#addition-of-primary-keys-to-join-tables"><span class="octicon octicon-link"></span></a>Addition of primary keys to join tables
<p>This facilitate the synchronizing of data having to do with many-to-many associations.</p>
<a class="anchor" href="#security-updates"><span class="octicon octicon-link"></span></a>Security Updates
<p>Miscellaneous security updates have been implemented, including</p>
<ul>
<li>Upgrading of Rails from version 3.0.18 to 3.2.21</li>
<li>Upgrading the default version of Ruby to version 2.1.5</li>
<li>Storage of session data in the database instead of in cookies</li>
<li>Elimination of most non-specific routes</li>
</ul>
<p>In keeping with recommended practice in Rails 3.2, packages that were formerly kept in vendor plugins are now in Ruby gems.</p>
<p>The change to database storage of session data has the additional benefit of overcoming some restrictions on the size of bulk uploads.</p>
<a class="anchor" href="#bug-fixes"><span class="octicon octicon-link"></span></a>Bug Fixes
<ul>
<li><p>The API for querying and downloading data offers more features than available previously, restoring some features that were lost in the upgrade from Rails 2 to Rails 3. See section 2 of the Data Access Guide: <a href="https://www.authorea.com/users/5574/articles/7062">https://www.authorea.com/users/5574/articles/7062</a></p></li>
<li><p>Cloning of PFTs now works again.</p></li>
<li><p>A bug that prevented editing a PFT if it was associated with some Prior whose paramb column was NULL has now been fixed.</p></li>
</ul>
<a class="anchor" href="#steps-needed-for-upgrade"><span class="octicon octicon-link"></span></a>Steps Needed for Upgrade
<a class="anchor" href="#database-changes"><span class="octicon octicon-link"></span></a>Database Changes
<p><strong><em>Administrators need to do database migrations!</em></strong></p>
<p>One migration has been added that adds id columns to the join tables.</p>
<p>The database version for this release is 20150202215147.</p>
<a class="anchor" href="#ruby-upgrade"><span class="octicon octicon-link"></span></a>Ruby Upgrade
<p>The officially-supported version of Ruby for use with BETYdb is now Ruby version 2.1.5. It is recommended that you upgrade to some Ruby 2 version since Ruby 1.9.3 is no longer being maintained. (See <a href="https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/">https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/</a> for details.)</p>
<p>Nevertheless, users who can not or do not wish to upgrade will likely be able to continue to use Ruby 1.9.3 without difficulty. It may also be possible to use the latest version of Ruby, Ruby 2.2.1.</p>
<a class="anchor" href="#to-continue-using-ruby-193"><span class="octicon octicon-link"></span></a>To continue using Ruby 1.9.3
<p>If you use RVM or some other Ruby version management system that reads the .ruby-version file, revert the string in that file so that it once again reads ruby-1.9.3-p429. You may wish to add .ruby-version to your .gitignore file so that git doesn't try to change it or flag it as having been modified.</p>
<a class="anchor" href="#to-upgrade-to-ruby-215"><span class="octicon octicon-link"></span></a>To upgrade to Ruby 2.1.5
<p>Install Ruby 2.1.5 if you haven't done so already. If you use RVM, you may do this by running</p>
rvm install 2.1.5
<p>If you run BETYdb with Apache httpd, change or add the directive</p>
PassengerDefaultRuby /path/to/ruby2/executable
<p>or the</p>
PassengerRuby /path/to/ruby2/executable
<p>directive according to your needs.</p>
<p>Otherwise, if you only use WEBrick, just ensure that the version of Ruby you want to use is first in your path. If you are using RVM, this is automatic (though you may have to leave and then return to the BETYdb Rails root directory if you haven't done so since updating your .ruby-version file; run rvm current to verify that you are using the correct Ruby version and gemset).</p>
<a class="anchor" href="#gem-installation-including-rails-upgrade"><span class="octicon octicon-link"></span></a>Gem Installation, Including Rails Upgrade
<p><strong><em>Administrators need to run the bundler to install several new Ruby Gems and updated versions of existing ones.</em></strong></p>
<p>First, change to the root directory of your BETYdb Rails installation. Then, if you are using RVM, run rvm current to ensure you are using the correct Ruby version and gemset. It should say ruby-2.1.5@betydb_rails3 if you upgraded Ruby and ruby-1.9.3-p429@betydb_rails3 if you did not. If you are not using a Ruby version management system, simply run ruby -v to check your version of Ruby.</p>
<p>Once you ensure you are using the correct Ruby version and gemset, run</p>
bundle
<p>If you have trouble installing capybara-webkit and don't need to run the Javascript-based RSpec tests, you may run</p>
bundle --without javascript_testing
<p>instead. If you won't be running RSpec tests at all and want to minimize your Gem installation, run</p>
bundle --without javascript_testing test debug
<p>See <a href="https://github.com/PecanProject/bety/wiki/Installing-the-BetyDB-Rails-Application#minimizing-gem-installation">https://github.com/PecanProject/bety/wiki/Installing-the-BetyDB-Rails-Application#minimizing-gem-installation</a> for details.</p>
<a class="anchor" href="#status-of-rspec-tests"><span class="octicon octicon-link"></span></a>Status of RSpec Tests
<ul>
<li>
<p>All tests continue to pass when run in the default environment and can be run using the command</p>
bundle exec rspec
</li>
</ul>
<p>Complete details for running the rspec tests are on the updated Wiki page at <a href="https://github.com/PecanProject/bety/wiki/Automated-Tests">https://github.com/PecanProject/bety/wiki/Automated-Tests</a></p>
Surat tugas, BAP, Presensi, Nilai CSL 2 Smt Genap 2024_2025 Bety SL
No full textKinerja pembelajaran Smt Genap TA 2024_2025 Bety SL FK UHAMK
bety: BETYdb 3.2.4
No full text<p>This incorporates some features and bug fixes from the September 29, 2014 sprint. It was deployed to <a href="http://www.betydb.org">www.betydb.org</a> on October 9, 2014.</p>
<a name="user-content-changes-pertinent-to-pecan-users" class="anchor" href="#changes-pertinent-to-pecan-users"><span class="octicon octicon-link"></span></a>Changes Pertinent to PEcAn Users
<p><strong><em>Administrators need to do database migrations!</em></strong><br>
See "Database Changes" below.</p>
<p>A constraint was added to the geometry column of the sites table to ensure the geometry is valid.</p>
<a name="user-content-release-highlights" class="anchor" href="#release-highlights"><span class="octicon octicon-link"></span></a>Release Highlights
<ul>
<li>The update.psql.sh script has been updated to incorporate changes to the corresponding pecan script—namely, it now adds a set of default users having all possible permission levels and adds the guestuser account.</li>
</ul>
<a name="user-content-summary-of-changes" class="anchor" href="#summary-of-changes"><span class="octicon octicon-link"></span></a>Summary of Changes
<a name="user-content-database-changes" class="anchor" href="#database-changes"><span class="octicon octicon-link"></span></a>Database Changes
<p><strong><em>Administrators need to do database migrations!</em></strong></p>
<p>The database version for this release is 20141009160121.</p>
<ul>
<li>A constraint was added to the geometry column of the sites table to ensure the geometry is valid.</li>
</ul>
<a name="user-content-minor-changes-and-improvements" class="anchor" href="#minor-changes-and-improvements"><span class="octicon octicon-link"></span></a>Minor Changes and Improvements
<ul>
<li>Contact information on the home page has been updated.</li>
<li>Instructions for citing BetyDB have changed.</li>
</ul>
<a name="user-content-bug-fixes" class="anchor" href="#bug-fixes"><span class="octicon octicon-link"></span></a>Bug Fixes
<ul>
<li>Redundant error messages are no longer displayed on the home page when login fails.</li>
</ul>
<a name="user-content-status-of-rspec-tests" class="anchor" href="#status-of-rspec-tests"><span class="octicon octicon-link"></span></a>Status of RSpec Tests
<ul>
<li>
<p>All tests now pass when run in the default environment and can be run using the command</p>
rspec
<p>Complete details for running the rspec tests are on the updated Wiki page at <a href="https://github.com/PecanProject/bety/wiki/Testing">https://github.com/PecanProject/bety/wiki/Testing</a></p>
</li>
</ul>
bety: BETYdb 4.1 New Database Uniqueness Constraints
No full text<p>New uniqueness constraints for database tables and validations for corresponding models; new RSpec tests; several bug fixes.</p>
<p>This release implements several value and uniqueness constraints on database tables aimed at ensuring that the BETYdb database will not contain multiple rows describing the same citation, site, species, treatment, or other entity. In conjunction with the database changes, new model validations have been added to several of the models so that potentially invalid database insertions or updates are caught at the Rails level before the insertion or update is attempted on the database.</p>
<p>Second, several bugs existed that prevented access to many pages of the site--especially pages for editing database entities. Many of these were introduced by changes to the routing file that eliminated most wildcard routes. These bugs have now been fixed and several new tests have been added to ensure these bugs don't re-appear.</p>
<a class="anchor" href="#changes-pertinent-to-pecan-users"><span class="octicon octicon-link"></span></a>Changes Pertinent to PEcAn Users
<p><strong><em>Administrators need to do a database migration.</em></strong></p>
<p>See "Database Changes" below.</p>
<a class="anchor" href="#summary-of-changes"><span class="octicon octicon-link"></span></a>Summary of Changes
<a class="anchor" href="#new-features"><span class="octicon octicon-link"></span></a>New Features
<a class="anchor" href="#new-validations-to-prevent-duplicate-rows-and-missing-data"><span class="octicon octicon-link"></span></a>New Validations to Prevent Duplicate Rows and Missing Data
<a class="anchor" href="#bug-fixes"><span class="octicon octicon-link"></span></a>Bug Fixes
<ul>
<li>Many pages that were previously inaccessible are once again reachable. Prior to this update, attempting to visit these pages yielded the following error:</li>
</ul>
The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.
<p>Affected pages included (for example)</p>
<ul>
<li>the Covariate editing page</li>
<li>the Model editing page</li>
<li>the Modeltype editing page</li>
<li>the Species editing page</li>
<li>the Traits editing page</li>
</ul>
<a class="anchor" href="#steps-needed-for-upgrade"><span class="octicon octicon-link"></span></a>Steps Needed for Upgrade
<a class="anchor" href="#database-changes"><span class="octicon octicon-link"></span></a>Database Changes
<p><strong><em>Administrators need to do database migrations!</em></strong></p>
<p>One migration has been added that new value and uniqueness constraints and also adds some convenience functions for implementing these constraints.</p>
<p>The database version for this release is 20150202220519.</p>
<a class="anchor" href="#status-of-rspec-tests"><span class="octicon octicon-link"></span></a>Status of RSpec Tests
<ul>
<li>
<p>All tests continue to pass when run in the default environment and can be run using the command</p>
bundle exec rspec
</li>
</ul>
<p>Every effort has been made to make this command idempotent: You should be able to run the tests multiple times without reloading the test fixtures between runs.</p>
<p>Complete details for running the rspec tests are on the updated Wiki page at <a href="https://github.com/PecanProject/bety/wiki/Automated-Tests">https://github.com/PecanProject/bety/wiki/Automated-Tests</a></p>
bety: BETYdb 4.2.1 Critical update to fix SQL constraints
No full text<p>This is a critical update to correct SQL functions; it also includes miscellaneous other changes.</p>
<p>The primary motivation for this release is to correct id-getting SQL functions that are being used to implement a distributed foreign-key constraint on the dbfiles table. Without this fix, non-EBI users will be unable to import data. A database migration corrects the problem functions.</p>
<p>Two other migrations are included: The first adds columns to the machines table having to do with data synchronization. The second implements default values on timestamp columns which historically have often been left as NULL.</p>
<p>Also included is a major feature addtion: the ability to generate and update database schema documentation using a rake task that runs SchemaSpy.</p>
<a class="anchor" href="#changes-pertinent-to-pecan-users"><span class="octicon octicon-link"></span></a>Changes Pertinent to PEcAn Users
<p><strong><em>Administrators need to do a database migration.</em></strong></p>
<p>See "Database Changes" below.</p>
<a class="anchor" href="#summary-of-changes"><span class="octicon octicon-link"></span></a>Summary of Changes
<a class="anchor" href="#new-features"><span class="octicon octicon-link"></span></a>New Features
<a class="anchor" href="#rake-task-to-generate-database-schema-documentation"><span class="octicon octicon-link"></span></a>Rake task to generate database schema documentation
<p>Database schema documentation is viewable from the Rails app by selecting "Schema" in the "Docs" menu. But up until now, this documentation has not been kept up to date. Now, up-to-date documentation can be generated using the "rake bety:dbdocs" task.</p>
<a class="anchor" href="#bug-fixes"><span class="octicon octicon-link"></span></a>Bug Fixes
<ul>
<li><p>The above-mentioned migration fixes a problem with SQL functions that would prevent users from importing data to their own copies of the BETYdb database (GH issue #327).</p></li>
<li><p>A long-standing error in the way the traits list page was displayed for users with "Viewer" status has been fixed (GH issue #299).</p></li>
</ul>
<a class="anchor" href="#steps-needed-for-upgrade"><span class="octicon octicon-link"></span></a>Steps Needed for Upgrade
<a class="anchor" href="#database-changes"><span class="octicon octicon-link"></span></a>Database Changes
<p><strong><em>Administrators need to do database migrations!</em></strong></p>
<p>There are three migrations in this release (see descriptions above).</p>
<p>The database version for this release is 20150625184958.</p>
<a class="anchor" href="#status-of-rspec-tests"><span class="octicon octicon-link"></span></a>Status of RSpec Tests
<ul>
<li>
<p>All tests continue to pass when run in the default environment and can be run using the command</p>
bundle exec rspec
</li>
</ul>
<p>Complete details for running the rspec tests are on the updated Wiki page at <a href="https://github.com/PecanProject/bety/wiki/Automated-Tests">https://github.com/PecanProject/bety/wiki/Automated-Tests</a></p>
bety: BETYdb 3.2.3
No full text<p>This adds a migration, restoring some defaults for column values that were lost in the migration from MySQL to PostgreSQL. It was deployed to <a href="http://www.betydb.org">www.betydb.org</a> on September 19, 2014.</p>
<a name="user-content-summary-of-changes" class="anchor" href="#summary-of-changes"><span class="octicon octicon-link"></span></a>Summary of Changes
<a name="user-content-database-changes" class="anchor" href="#database-changes"><span class="octicon octicon-link"></span></a>Database Changes
<p><strong><em>Administrators may need to do database migrations if they wish to sync their database with the one on ebi-forecast.</em></strong></p>
<p>The database version for this release is 20140915153555.</p>
<ul>
<li><p>This is a very minor migration: It sets three default values:</p></li>
</ul><ol>
<li>a default of 0 for the <em>checked</em> column of the traits table</li>
<li>a default of 0 for the <em>checked</em> column of the yields table</li>
<li>a default of '' for the <em>name</em> column of the users table</li>
</ol><p>This restores defaults that were set in the MySQL version of the database before it was migrated to PostgreSQL.</p>
- …
