This project forked from dickinsoncollege/farmdata2
FarmData2 provides support for the operation and certification requirements of small organic farming operations.
License: Other
A user may have all selected for Type of Seeding, but may have selected a crop or area that only has Tray or Direct Seedings. When this happens the other summary will show 0 or NaN (not a number), instead have that summary show a message: “There are no [Tray or Direct] Seedings in the options you have chosen.”
To test this go to the Seedings Report subtab under BarnKit tab, which is on the home page. Selected a date range, and try filtering different Areas and Crops.
An example is shown below:
This issue is complete when the message appears in Tray and Direct seeding summaries, when there are no current logs in the respective summaries.
Friday Jul 23, 2021 at 18:33 GMT
Originally opened as DickinsonCollege#259
Description: When creating a new Seeding Input Log, it is possible to enter values that are invalid, such as negative numbers and decimal values that do not make sense in certain categories (e.g. Workers: 9.4).
Directions to Replicate the Bug
Expected Results: The application should not let the user submit these values and should give the user an error message that notifies them of the appropriate values that they should input.
Observed Results: The application allows the user to submit these invalid values and stores this Seeding Input Log with the rest of the data.
Saturday Dec 11, 2021 at 21:42 GMT
Originally opened as DickinsonCollege#333
Move FarmData2 to its own organization or clean up the Dickinson Organization to remove student course repositories. Also, consider creating organization defaults for licenses, code of conduct, etc
Friday Oct 09, 2020 at 19:40 GMT
Originally opened as DickinsonCollege#10
Description: When the date range from April 14th 2020-August 20th 2020 are fed into the seeding report, some of the output dates are ordered incorrectly.
Direction to replicate:
Expected result: The date for crops like peppers should be shown planted as they are in the Seeding report.
Observed result: We see a different date than what we expected.
The seeding report page hides everything but the date selection section when new dates are being chosen. Currently, the rest of the page disappears once the input has been changed and then clicked off of, instead of right after the initial click.
There are two possible solutions:
Friday Jul 23, 2021 at 20:31 GMT
Originally opened as DickinsonCollege#274
The comment at the bottom of the form states "* All inputs with astrix are required and must be filled before submitting the report" This should be rephrased to be: "* required field."
The code for the seeding input log is found in farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html
Monday Oct 04, 2021 at 14:24 GMT
Originally opened as DickinsonCollege#287
The Area drop down in the Seeding Input form contains duplicates. The same list of areas appears to be being appended to the dropdown multiple times. Each Area should appear in this list only one time.
Steps to Reproduce
Based on the above behavior this appears to have something to do with the way the caching is done for areas. It should be compared to what is being done for the crops which are not exhibiting the same behavior.
Tuesday Jun 07, 2022 at 13:06 GMT
Originally opened as DickinsonCollege#460
The Bug Reports and Feature Requests sections of the CONTRIBUTING.md file should have links to some documents that describe how to write a good bug report or how to write a good feature request.
Related to #11, #12. If good documents are found then templates could be produced to match.
Sunday Jan 10, 2021 at 19:36 GMT
Originally opened as DickinsonCollege#94
Description: The seeding report in Barnkit of FarmData2 produces incorrect results when invalid dates are entered for startDate and endDate, such as 02/31/yyyy - mm/dd/yyyy, 11/31/2021- mm/dd/yyyy (The characters in this two example can be represented by any month, date, or year). The invalid dates can only be entered by typing directly into the input box and cannot be achieved using the calendar function.
It seems like most of the errors occur because a nonexistent day in a month has been entered. Also, entering a day that has not happened yet will cause an error as well. When errors occur, the report that will be generated are all identical.
PS: The original farmdata1 might contain this issue as well. An invalid date such as February 31 can be used to search, but I cannot give a definite conclusion as I wasn't able to test further with the guest edition.
Directions to Reproduce:
Expected result: Shown and described in the picture.
Actual result: Shown and described in the pictures.
Friday Apr 29, 2022 at 16:45 GMT
Originally opened as DickinsonCollege#451
The default for the feet unit (inside the Direct Seeding inputs) should be bed. It defaults to blank right now.
To test this go to the Seedings Input subtab under FieldKit tab, which is on the home page.
The code can be found by going to farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html file.
Friday Jul 23, 2021 at 20:17 GMT
Originally opened as DickinsonCollege#271
Description : When searching reports by Seeding report, some reports are return not in date order
Direction to Replicate the bug :
Expect result:each value of table should be sorted by date, which reports at 2020-05-22 should appear before reports at 2020-06-17
Observed result: reports at 2020-06-17 appears before 2020-05-22
Description: On the Seeding Report page, when certain date ranges are used, the dates of the seeding logs within this range are not sorted in proper ascending order.
Steps to Replicate this Issue:
Expected Result:
Observed Result:
Description:- The main table in Seeding Repot is supposed to be sorted by the values in date column (Earlier dates come first). However, when searching for a fairly wide date range, there will be case where some rows of later dates come before a row of earlier dates.
Directions to Replicate the Bug
1. Open the FarmData2 Application
2. Click on the Seeding Report button in the BarnKit Tab
3. Give a fairly wide range of dates
4. Click Generate Report
Expected Result : The application should show a main table in which all the rows are properly sorted according to there respective values in the date column.
Observed Results: The application showed a main table where some rows with later dates appeared before a row with earlier date.
Between certain date ranges the some of the seeding reports are not sorted correctly. This problem effects different entries depending on the date ranges, but remains consistent when revisiting the same date ranges.
Example 1:
Example 2:
In this example (dates from 06/01/2020-07/10/2020) each entry is a tray seeding yet the dates are still out of order.
It appears as if the direct tray seedings are listed first no matter the dates listed, but keep in mind this is not the case in example 2.
The expected result would be a properly sorted list of all seeding types and in any date range.
In certain date ranges the dates in the seeding report will be out of order.
All direct seedings are listed first in order no matter dates.
When viewing the Seeding Report from specific date ranges, the seeding logs are not correctly ordered by date.
The seeding logs should be ordered, with older logs above newer logs, in the Seeding Report table.
If there are no logs in the table then the filters, table, and summaries do not show up. The page where they should be is just blank. Instead we want there to be a message saying “There are no logs in the time range you have selected. Please select new dates.”
There are two scenarios when the filters, table, and summaries disappear. First is when there are no logs within the date range, the second is when the user deletes all the logs in the date range. This is likely due to there being no logs in the array seedingLogs.
To test this go to the Seedings Report subtab under BarnKit tab, which is on the home page.
Friday Jul 23, 2021 at 17:56 GMT
Originally opened as DickinsonCollege#258
The "Info" subtab on the Barn Kit tab should appear on the left. The Seeding Report sub-tab should appear to the right. This ordering is controlled by the weights assigned in the farmdata2_modules/fd2_tabs/fd2_barn_kit.module file.
Wednesday Sep 22, 2021 at 12:19 GMT
Originally opened as DickinsonCollege#283
 |
|---|
| Red highlight indicates the existence of an extra space. |
 |
|---|
| Notice: Red highlight is gone because the extra space has been deleted. |
Tuesday Jun 28, 2022 at 20:18 GMT
Originally opened as DickinsonCollege#507
The main table on the seeding report page isn't sorted by the values in the date column. Notice how in the example below, the row corresponding to 2020-05-06 comes after the one corresponding to 2020-05-20.
To recreate this example:
Which columns in the seeding report should be editable and when?
Tuesday Jun 07, 2022 at 19:37 GMT
Originally opened as DickinsonCollege#466
Description: When the date range April 2020-August 2022 is input into the Seeding Report, some of the dates are inaccurately ordered in ascending order.
Direction to replicate this result
Expected Result : We can expect that the date for the peppers in ALF-2 would be 2020-05-04 as a result of their location in the seeding report.
Observed Result : We can observe that the date for the peppers in ALF-2 is 2022-05-26 according to the seeding report.
The Data section should be broken up into two sections, with the date, crop, comments, and area in the first section. The second section should have everything else and be after the Tray/Direct Seeding section. The second section should be called something other than data.
To test this go to the Seedings Input subtab under FieldKit tab, which is on the home page.
The code can be found by going to farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html file.
Friday Jul 23, 2021 at 20:30 GMT
Originally opened as DickinsonCollege#273
By default farmOS displays tabs for Reports and Quick forms that are not relevant to FarmData2. These tabs should be removed from the UI.
Wednesday Jan 05, 2022 at 16:22 GMT
Originally opened as DickinsonCollege#370
Review FarmData2 documents with respect to inclusivity of language. This issue has been created proactively rather than reactively. Pull requests with language revisions for review are welcome.
See "Google’s initiative for more inclusive language in open source projects" for some ideas of what to look for and revisions that might be made as necessary:
Tuesday Nov 10, 2020 at 20:59 GMT
Originally opened as DickinsonCollege#32
Currently if you visit the documentation for the various methods and components for this project in global.html you will see the following information describing what each prop in the component does.
In the box, the phrase "not support those attributes" is a little vague and should be more explicit.
./doc.bash command.The desired results would look something like this:
Thursday Jun 23, 2022 at 17:47 GMT
Originally opened as DickinsonCollege#502
Description: The Tray Seeding Summary in Seeding Report, sometimes produces the output - NaN (Not a Number) for “Total Number of Tray Seeds Planted” and “Average Seeds Planted per Hour” instead of proper values. The issue occurs only for the dates 05/13/2019 and 06/13/2019. However, when we search for the date ranges 05/14/2019 to 06/12/2019 the NaN error doesn’t occur but has proper values.
Directions:
Expected Result: The Tray Seeding Summary shouldn't have the output NaN instead of proper values (i.e. 5000).
Observed Result: The incorrect output occurs only when the date ranges contain 05/13/2019 or 06/13/2019.
Description: Users could enter invalid input data for checking Seeding Report in BarnKit tab
Steps to replicate the error:
When it comes to this page, there is no alerts for entering such non-sense dates.
Only shows up error when people click on "Generate Report" button.
Oberseved output
Desired output: Users should not be allowed to choose inputs for year that is earlier than the creation of the farm or laster than today's date.
Saturday Dec 18, 2021 at 08:11 GMT
Originally opened as DickinsonCollege#347
The primary steps of the GitFlow workflow are outlined here. They could be augmented with links for each of the steps so that they would be useful to relative new comers to FOSS. GitHub provides useful help pages for each of these steps that can be found and linked.
Monday Nov 16, 2020 at 16:52 GMT
Originally opened as DickinsonCollege#34
In the Tray Seeding Summary which is indicated at the bottom of the Seeding Report, sometimes the value of the "Total Number of Tray Seed Planted" and "Average Seeds Planted per Hour" displays "NaN" (Not a number) instead of proper values (such as positive real number)
1. Login into FarmData2
2. Click "BarnKit" from the bar
3. Click "Seeding Report"
4. Insert the Start Date as 05/01/2019
5. Insert the End Date as 11/02/2020
6. Click "Generate Report"
7. Scroll down to the very bottom
8. Wait for the result comes out
9. Check "Tray Seeding Summary"
The value of "Total Number of Tray Seed Planted" and "Average Seeds Planted per Hour" is "NaN"
The value of "Total Number of Tray Seed Planted" and "Average Seeds Planted per Hour" should be a positive real number.
Description:
The order in which values are sorted in the Seeding Report are not ordered from oldest to newest depending on the date range chosen.
Reproduction Steps:
Expected Result:
The values should be ordered from oldest to newest throughout the report. For example, 2019-05-30 should come before 2019-05-31 as it is an older date.
Observed Result:
Throughout the values, there are instances of a value with a newer date showing up before an older date. For example, 2019-06-06 comes before 2019-05-30, despite being the newer date.
The Bug:
In the Seeding Report, for date ranges that contain dates between 05/13/2019 and 06/13/2019, the Tray Seeding Summary at the bottom of the page show the values for "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" as being NaN (not a number). This does not make sense because there were tray seeds planted during the example time period given below.
To Reproduce:
What Should Happen:
This image is a picture of what the Tray Seeding Summary looks like if you use the date range 04/30/2019-05/12/2019, which seems to be correct:
What Does Happen:
This image shows what the Tray Seeding Summary looks like if you change the date range by one day to 04/30/2019-05/13/2019:
As far as I can tell, this only seems to happen for date ranges that include dates between 05/13/2019 and 06/13/2019.
Description
The main table in Seeding Report is supposed to be sorted by the values in the date column (Earlier dates come first). However, when searching for some specific time period, like from May 1st to May 31st 2020, there will be cases where some rows of later dates come before a row of earlier dates.
Replicate the Bug
Expected Result: The application should show the main table in which all the rows are sorted adequately according to the respective values in the date column.
Observed Results: The application showed the main table where some rows with later dates appeared before a row with an earlier date.
Description: Sometimes when Set Dates for Seeding reports, the results is not in date order.
Direction of procedure:
Expected: the date Jun 11th suppose to be on top
Observed: the date Jun 11th appear after Jun 17th
The summary tables that appear at the bottom of the Seeding Report should appear only after all of the data has been loaded. So while the data is loading the spinner should be the last element on the page. Once the data is loaded the spinner should disappear (as it currently does) and the summary table or tables should appear (related to DickinsonCollege#258 and DickinsonCollege#259). This modification should also include Cypress tests for the desired behavior.
Wednesday Sep 22, 2021 at 12:34 GMT
Originally opened as DickinsonCollege#284
Description: On certain date range, the values in the Seeding Report are not sorted from oldest to newest because the dates are not sorted from oldest to newest.
Step-By-Step Directions To Reproduce Bug:
Expected Result: The results should be displayed in the order from oldest to latest. Like observed in the screenshot below:
Observed Result: However, in some cases the newer date appears before the later date as observed in the screenshot below:
Description
In the Seeding Report found in the "BarnKit" section of FarmData2, occasionally - the logs are not sorted in chronological order of dates as is desired. This can be observed from the image:
Step-By-Step Directions To Reproduce Bug
Expected Result
The expected result should comprise a table consisting of seeding logs that are chronologically ordered. This means that seeding logs made earlier should be located higher up in the table than those made later, as can be seen from the following image:
Observed Result
Currently, it can be observed at multiple points that the ordering of seeding logs is not chronological. While one example of this has been provided in the description, here is another example provided in the following image:
Description: When creating a new Seeding Report with a specific Start Date, some of the outcome values in the Tray Seeding Summary for Total Number of Tray Seeds Planted and Average Seeds Planted per Hour report as NaN.
Directions to Replicate the Bug:
Expected Results: The Total Number of Tray Seeds Planted and Average Seeds Planted per Hour should show actual real numbers.
Observed Results: The Total Number of Tray Seeds Planted and Average Seeds Planted per Hour is showing NaN.
Description: Dates in Seeding Report's main table are not sorted in order when selecting long periods.
Replicating steps:
Expected Result: The web can display dates of crops in proper order
Observed Results: The web displays values in correct order (from longest to latest)
Description: When creating a new Seeding Report with a Start Date before May and End Date starting from June, the outcome values in the Tray Seeding Summary for Total Number of Tray Seeds Planted and Average Seeds Planted per Hour sections are inappropriate.
Directions to Replicate the Bug:
Expected Results: The Total Number of Tray Seeds Planted and Average Seeds Planted per Hour should show a proper value.
Observed Results: The Total Number of Tray Seeds Planted and Average Seeds Planted per Hour show NaN values instead.
Description: When looking at a large selection of dates (such as from 06/01/2019 to 10/01/2019), an error pops up in Tray Seeding Summary. Both "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" are reported as NaN.
Directions to Replicate:
Expected Results:
A number should appear in both sections that currently print NaN.
Observed Results:
NaN appears instead of a number in the two sections.
Description: When accessing to Seeding Report, it is possible that the Tray Seeding Summary shows invalid results(NaN). For example, in date range from 06/05/2019 to 12/10/2019, total number of tray seeds planted and average seeds planted per hour are invalid.
Directions to Replicate the Bug:
Expected result: The Tray Seeding Summary should show the proper results, which are positive numbers.
Observed result: Tray Seeding Summary shows NaN for "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour"
Description: Users are able to enter invalid inputs such as negative values into the Seeding Input Log of FieldKit
Steps to replicate this problem:
Observed Output
Desired Output
There should not be a bottom error option available to click to generate a negative value.
Thursday Dec 16, 2021 at 08:52 GMT
Originally opened as DickinsonCollege#344
The README.md file should be updated with links to the appropriate resources.
In additions, logos and images for GPL3, CC, farmOS, NPFI, NSF, GNOME might be added as well.
Saturday Oct 10, 2020 at 19:14 GMT
Originally opened as DickinsonCollege#16
Description
Directions to replicate the bug
Expected Result
Observed Result
The Direct Seeding Summary table that appears at the bottom of a Seeding Report contains a line for Total Row/Bed Planted. This metric not useful for farmers and clutters up the summary. Currently the summary table includes the Total Row/Bed Planted line which should be deleted:
To test this:
The desired result will be similar to the following, where the Total Row/Bed Planted line has been removed:
Friday Jul 23, 2021 at 18:50 GMT
Originally opened as DickinsonCollege#260
Sometimes in the Tray Seeding Summary table at the bottom of a Seeding Report, the “Total Number of Tray Seeds Planted” and “Average Seeds Planted per Hour” are reported as NaN (Not a Number) instead of the proper values. The different behaviors seem to be dependent on the date range.
The results should be a positive real numbers that are the actual Total Number of Tray Seeds Planted and Average Seeds Planted per Hour.
Instead the results are inputted as NaN in the Tray Seeding Summary table.
Description: When creating a new Seeding Input Log, it is possible to enter values that are invalid, such as negative numbers and decimal values that do not make sense in certain categories (e.g. Workers: 9.4).
Directions to Replicate the Bug
Expected Results: The application should not let the user submit these values and should give the user an error message that notifies them of the appropriate values that they should input.
Observed Results: The application allows the user to submit these invalid values and stores this Seeding Input Log with the rest of the data.
Saturday Dec 11, 2021 at 21:42 GMT
Originally opened as DickinsonCollege#333
On the Seeding Input form on the FieldKit tab, if the Area selected does not match the type of seeding that is chosen the Area will be cleared.
Steps to replicate:
Similarly, when the seeding type is changed from Direct Seeding to Tray Seeding or vice versa then the Area chosen for the seeding is erased.
Steps to replicate:
4. Continuing from the prior steps...
5. Choose the ALF field as the Area for the seeding.
6. Click the Tray Seeding radio button.
Discussion
This behavior makes sense in that it ensures that Direct Seedings can only occur in fields while Tray Seedings can only occur in greenhouses. However, the behavior is confusing for two reasons:
Desired Behavior
The desired behavior is for the Area dropdown to appear in the Tray Seeding or Direct Seeding portion of the form rather than in the Data (top) section of the form. This addresses both of the reasons for confusion outlined above:
This issue replaces DickinsonCollege#300.
Wednesday Dec 08, 2021 at 17:27 GMT
Originally opened as DickinsonCollege#322
The date ordering in the main seeding report is incorrect and inconsistent
Steps to reproduce
Table organized by consistent ascending order by date
Table is not organized in consistent ascending order, but instead shows reports from 2019 then 2020 then back to 2019...
Observed on Microsoft Windows 11 Home, Version 10.0.22000 Build 22000
The default start date for generating seeding reports should be the first day of the current year.
To reproduce:
Monday Jul 18, 2022 at 19:59 GMT
Originally opened as DickinsonCollege#539
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.