Last active
August 29, 2015 14:03
-
-
Save mbohun/af110bcd6e6178b7def3 to your computer and use it in GitHub Desktop.
code.google.com issues 2 github issues migration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[ | |
{ | |
"AllLabels": "FieldCapture, Priority-Critical, Type-Enhancement", | |
"ID": "434", | |
"Modified": "Jul 10, 2014 00:30:24", | |
"ModifiedTimestamp": "1404952224", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Critical", | |
"Status": "New", | |
"Summary": "Export project dashboard and all-project data as CSV download", | |
"Type": "Enhancement", | |
"details": [ | |
"\nWill need the ability to export both the project output data and all project data in a downloadable CSV format. \r\n\r\nNot required until Feb-Mar 2014.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Critical, Type-Enhancement", | |
"ID": "435", | |
"Modified": "Jul 10, 2014 00:04:23", | |
"ModifiedTimestamp": "1404950663", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Critical", | |
"Status": "New", | |
"Summary": "Export program output data and filtered all data as CSV", | |
"Type": "Enhancement", | |
"details": [ | |
"\nWill need the ability to export both the program output data and all project data for a filtered selection of projects in a downloadable CSV format. \r\n\r\nNot required until Mar 2014.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Critical, Type-Enhancement", | |
"ID": "583", | |
"Modified": "Jul 05, 2014 12:06:25", | |
"ModifiedTimestamp": "1404561985", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Critical", | |
"Status": "New", | |
"Summary": "Ability to change the site associated with an activity", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE ", | |
"\r\nWhen a plan has been approved and the recipient goes to report, they can't go back to the activity and re-assign the site to another site.\r\n\r\nComment - PB 14/2/14\r\nAbility to change the site associated with an activity is required, but need to handle the situation where photopoint data is attached to an activity.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Critical, Type-Task", | |
"ID": "751", | |
"Modified": "Jul 09, 2014 05:47:09", | |
"ModifiedTimestamp": "1404884829", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Critical", | |
"Status": "Accepted", | |
"Summary": "Change labels for fields on Project Information edit page", | |
"Type": "Task", | |
"details": [ | |
"\nThe following label changes are required on the Project Information edit page for the Green Army programme. These are more general than the terms currently used and should also apply adequately for other programmes.\r\n\r\n\"Grant recipient\" change to \"Recipient\"\r\n\"Funded by\" change to \"Programme\"\r\n\r\nA \"Service provider\" field also needs to be added to this page and this will also need to map into the \"Organisation\" facet on the site home page.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Critical, Type-Enhancement", | |
"ID": "534", | |
"Modified": "Jul 06, 2014 06:46:59", | |
"ModifiedTimestamp": "1404629219", | |
"Owner": "Sathish.Sathyamoorthy", | |
"Priority": "Critical", | |
"Status": "New", | |
"Summary": "Ability to locally save a PDF of stage reports at the point of report submission", | |
"Type": "Enhancement", | |
"details": [ | |
"\nGrantees need to be able to locally save (optional) a PDF version of the full stage report when they submit it to the AG, as a record for their own files. This should include:\r\n* copy of the Plans & reports tab\r\n* copy of all comments on cancelled and deferred activities, referenced back to the corresponding activities\r\n* copy of completed activity forms for all activities in the stage report\r\n* copy of the dashboard at the time of the report.\r\n\r\nUsers and AG staff should be able to reproduce this PDF document at any time. Need to consider implications of versioning, though date/time stamping the printed version with the submission data/time may be sufficient.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Critical, Type-Enhancement", | |
"ID": "539", | |
"Modified": "Jul 05, 2014 12:44:32", | |
"ModifiedTimestamp": "1404564272", | |
"Owner": "Sathish.Sathyamoorthy", | |
"Priority": "Critical", | |
"Status": "New", | |
"Summary": "Add a \"Project Management\" tab to the project view", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE have requested that provision to record other project management information also be included - eg. project objectives, project methodology, risk management, etc.\r\n\r\nThis would be best provisioned by adding a \"Project management\" tab to the project view.\r\n\r\nPriority is currently low and real need is still to be clarified, as does actual content.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "Layers, Priority-High, Spatial-Portal, SpatialPortal, Type-Enhancement", | |
"ID": "58", | |
"Modified": "May 27, 2014 02:00:09", | |
"ModifiedTimestamp": "1401156009", | |
"Owner": "adam.collins832", | |
"Priority": "High", | |
"Status": "Started", | |
"Summary": "Load Layer: States and Territories Polygons 2011", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Defect", | |
"ID": "547", | |
"Modified": "Mar 24, 2014 02:41:55", | |
"ModifiedTimestamp": "1395628915", | |
"Owner": "adam.collins832", | |
"Priority": "High", | |
"Status": "Started", | |
"Summary": "Tabulations outstanding issues", | |
"Type": "Defect", | |
"details": [ | |
"\nIn writing a Case Study on Tabulations (Tools | Tabulate), I note a number of outstanding Tabulation issues\r\n\r\n1. Defect: The drop down list includes a typo \"Tillage practive - dominant (area)(class)\". I am unsure where the list comes from as it is ok in the Layers Table (where I can edit it).\r\n\r\n2. Enhancement: The tabulations are currently missing the contextual layers\r\n\r\n Surface geology (#60 Miles to get 250m grid data from Kristen Williams)\r\n Koppen Climate Classification*\r\n Koppen Climate Classification \u2013 sub areas*\r\n Land Cover Type \u2013 IGBP (2011)*\r\n\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Defect", | |
"ID": "674", | |
"Modified": "Jul 07, 2014 23:09:26", | |
"ModifiedTimestamp": "1404774566", | |
"Owner": "adam.collins832", | |
"Priority": "High", | |
"Status": "Started", | |
"Summary": "Export area fails on all formats (shapefile, KML and WKT) formats", | |
"Type": "Defect", | |
"details": [ | |
"\nExport | Areas fails on \r\n\r\n1. shapefile (see attached error)\r\n2. KML (nothing happens)\r\n3. zip file produced with 24 bytes containing in test case\r\n\r\n\"ENVELOPE(cl1048,5746755)\"\r\n\r\nI generated 4 areas (called My Area 1-4) from adjacent IBRA-7 regions and then did a areas merge (called Merged 1-4 - which wasn't used further here but just for the record). I then tried to export Area 1, Area 2, Area 3 and Area 4 using shapefile, KML and WKT and got consistent fails as noted above.\r\n\r\n\r\n\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Defect", | |
"ID": "728", | |
"Modified": "Jul 08, 2014 02:17:56", | |
"ModifiedTimestamp": "1404785876", | |
"Owner": "adam.collins832", | |
"Priority": "High", | |
"Status": "Started", | |
"Summary": "Adding species list adding a single polygon to map", | |
"Type": "Defect", | |
"details": [ | |
"\nI think this is only happening when a user adds a list to the map with taxa having an expert distribution:\r\n\r\n", | |
"\r\n\r\nI dont think this is the desired behaviour.\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Layers, Priority-High, Spatial-Portal, SpatialPortal, Type-Enhancement", | |
"ID": "59", | |
"Modified": "May 27, 2014 02:29:48", | |
"ModifiedTimestamp": "1401157788", | |
"Owner": "adam.collins832", | |
"Priority": "High", | |
"Status": "OnDev", | |
"Summary": "Load Layer: dis_coast_me", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "418", | |
"Modified": "Jul 04, 2014 06:59:36", | |
"ModifiedTimestamp": "1404457176", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Photopoint photo upload needs to use the document upload mechanism", | |
"Type": "Defect", | |
"details": [ | |
"\nCurrently the file is being saved on the fieldcapture server & filename clashes are not tested for.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "493", | |
"Modified": "Jan 24, 2014 03:48:48", | |
"ModifiedTimestamp": "1390535328", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "FieldCapture Mobile", | |
"Type": "Enhancement", | |
"details": [ | |
"\nMobile capability for field-based data recording based on MERIT forms.\r\n\r\nWill be required for implementation of the Green Army programme and likely to have a high political profile.\r\n\r\nThis is not urgent, but is likely to be required around March/April 2014, with perhaps an early demonstrator version in March.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "517", | |
"Modified": "Jul 05, 2014 12:24:03", | |
"ModifiedTimestamp": "1404563043", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Selective association of activities with programs/sub-programs", | |
"Type": "Enhancement", | |
"details": [ | |
"\nNew requirements for activities under the Green Army programme suggest that we need to be able to selectively associate activities with programs and perhaps even sub-programs so that only activities relevant to a particular program are selectable in that program context.\r\n\r\nThis would also facilitate some requirements for BDRS migration.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "532", | |
"Modified": "Jan 17, 2014 06:24:28", | |
"ModifiedTimestamp": "1389939868", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Can re-submit create requests during processing of site save", | |
"Type": "Defect", | |
"details": [ | |
"\nThe process for saving sites can take a while and there is currently no indicator to show that the system is processing the request. It is therefore very easy for second and third requests to be made during the processing which create copies of the site being saved. \r\n\r\nIn concert with issue 5?? this creates confusion and potential issues in the data.\r\n\r\nNeed to subsequent submit actions whilst a site is being saved and also display a processing indicator while the process is running.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "563", | |
"Modified": "Jul 05, 2014 12:41:18", | |
"ModifiedTimestamp": "1404564078", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Case study tab on home page", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE requirement #47\r\nCase studies to be displayed as additional tab on home page. Projects to nominate if they would like to be a case study when submitting reports. (links with ", | |
" (DoE#27))\r\n\r\nComment - PB 6/2/14\r\nThis would probably be a rolled-up listing of truncated project narratives (see ", | |
") with a \"show more\" link to the project overview page containing the full story, and maybe also icons to flag whether images and video media are attached to a particular project.\r\nThe listing should be responsive to the keyword search and filter selections like other tabs on the home page.\r\n\r\nNote that ", | |
" will likely need further enhancement to fully satisfy the requirement.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "574", | |
"Modified": "Jul 05, 2014 12:30:28", | |
"ModifiedTimestamp": "1404563428", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Add project and sites components of the data model to the API doco", | |
"Type": "Enhancement", | |
"details": [ | |
"\nCurrently the API documentation does not show the \"project\" and \"sites\" parts of the data model and it is therefore incomplete.\r\n\r\nExternal systems wanting to inter-operate with fieldcapture will need to map some of their data to these components.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "598", | |
"Modified": "Jul 04, 2014 06:51:26", | |
"ModifiedTimestamp": "1404456686", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Can't display large view of photo point images ", | |
"Type": "Defect", | |
"details": [ | |
"\nOnce photo point images are loaded they appear only as small thumbnails with no way of viewing them as a larger image.\r\n\r\nNeed to view these images (including attribution and description, which is not currently collected with the image), in a large format modal popup.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "683", | |
"Modified": "Jul 04, 2014 06:44:22", | |
"ModifiedTimestamp": "1404456262", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Date sequencing in the gantt view is reversed within a stage section", | |
"Type": "Defect", | |
"details": [ | |
"\nSee image attached.\r\n\r\nThe sequencing of activities within a stage section appears to be in reverse chronological order of start date. This should just be in chronological order.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "731", | |
"Modified": "Jul 04, 2014 07:36:58", | |
"ModifiedTimestamp": "1404459418", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Home page tab for DoE only custom reports", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE have a requirement for a number of specific operational reports to be generated on-call from MERIT data. These are different from dashboard activity-based reports and includes, though not limited to:\r\n1) current user list sortable/filterable by user role and permission - this is need for assessing periodic clean-up of internal staff access and permissions.\r\n2) Project stats by state - needed for monitoring DoE regional office operational efficiency\r\netc.\r\n\r\nSpecific requirements, presentation styles, and more report types still to come.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "734", | |
"Modified": "Jul 06, 2014 03:45:35", | |
"ModifiedTimestamp": "1404618335", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Change 'State' spatial filter from just the terrestrial state layer to state terrestrial plus adjacent coastal waters", | |
"Type": "Defect", | |
"details": [ | |
"\nWhen applying the 'state' filter, project/activity sites which occur offshore (eg. GB Reef, Torres Straight, etc.) are excluded from the selection and hance the result set. This issue has been raised several times by DoE.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "745", | |
"Modified": "Jul 07, 2014 04:21:10", | |
"ModifiedTimestamp": "1404706870", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Project outputs are incongruent with project dashboard and not updating correctly", | |
"Type": "Defect", | |
"details": [ | |
"\nUser submitted issue (via DoE #36):\r\n\r\nThe project outputs do not display correctly and appear not to necessarily guide the project dashboard.\r\n\r\nValues in the project dashboard are also not updating correctly.\r\n\r\nSee MERIT Demonstrator project in TEST\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "344", | |
"Modified": "Dec 16, 2013 03:18:33", | |
"ModifiedTimestamp": "1387163913", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Revise workflow for the Photo Points output", | |
"Type": "Defect", | |
"details": [ | |
"\nPhotopoints are likely to require some thought as to the workflow rather than just a normal output\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "665", | |
"Modified": "Jul 05, 2014 12:00:44", | |
"ModifiedTimestamp": "1404561644", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Changes requested for MERIT programme dashboard", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE have requested a number of changes in the programme dashboard. Some of these have been addressed already, but some programatic changes are also required - see attached.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "491", | |
"Modified": "Jul 06, 2014 06:59:21", | |
"ModifiedTimestamp": "1404629961", | |
"Owner": "chris.godwin.ala", | |
"Priority": "High", | |
"Status": "Started", | |
"Summary": "Check for and update validation of numeric fields in forms.", | |
"Type": "Defect", | |
"details": [ | |
"\nI can default numeric types to use \"must be a number\" validation, however validation rules will need to be manually applied where missing for integers or >= 0.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "742", | |
"Modified": "Jul 06, 2014 04:58:46", | |
"ModifiedTimestamp": "1404622726", | |
"Owner": "CoolDad67", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Enable projects to be 'closed' and selectively filtered in search/display results", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE requirement #122\r\n\r\nNeed to be able to flag projects as 'finished' or 'closed' and to selectively filter them individually or together in/out of filtered search results.\r\n\r\nCurrently awaiting a definition of a 'closed' project from DoE.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Defect", | |
"ID": "744", | |
"Modified": "Jul 06, 2014 05:05:01", | |
"ModifiedTimestamp": "1404623101", | |
"Owner": "CoolDad67", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "User could submit a stage report with \"Started\" activity status on some activities", | |
"Type": "Defect", | |
"details": [ | |
"\nUser submitted issue (via DoE #99):\r\n\r\nProject LSP 876 submitted a report even though there were activities listed as \"Started\".\r\n\r\nNeed to test!\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Task", | |
"ID": "226", | |
"Modified": "Aug 13, 2013 00:07:05", | |
"ModifiedTimestamp": "1376352425", | |
"Owner": "drdavematthews", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Fix geonetwork configuration", | |
"Type": "Task", | |
"details": [ | |
"\nHi Dave,\r\n\r\nWe've discovered a couple of configuration problems with geonetwork - could you please take a look at these when you get a chance?\r\n\r\nGeonetwork is installed at /usr/local/geonetwork on both ala-maps and ala-devmaps. I have made a short wiki page about it here: ", | |
"\r\n\r\n1. Geonetwork does not automatically start up when ala-maps or ala-devmaps is started. Could you add this to the list of programs that are started on start-up? /usr/local/geonetwork/bin/start-geonetwork.sh needs to be run to start the bundled jetty instance that serves geonetwork.\r\n\r\n2. I cannot access the dev instance of geonetwork via spatial-dev.ala.org.au/geonetwork. I can access it while logged into dev by running wget http://localhost:8084/geonetwork I think this is some kind of forwarding issue as the 404 page that I get is served by tomcat. The jetty instance running geonetwork is located at: /usr/local/geonetwork/jetty\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "320", | |
"Modified": "Jan 24, 2014 03:58:25", | |
"ModifiedTimestamp": "1390535905", | |
"Owner": "[email protected]", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Edit document functionality", | |
"Type": "Enhancement", | |
"details": [ | |
"\nAdd the ability to edit the document metadata.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-High, Type-Enhancement", | |
"ID": "262", | |
"Modified": "Jul 17, 2014 05:42:58", | |
"ModifiedTimestamp": "1405575778", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "An invasive/pest/weed/introduction/alien status facet needed to parallel Conservation status facet", | |
"Type": "Enhancement", | |
"details": [ | |
"\nWe need a way of identifying an invasive/alien/pest/weed species observed in the same way that we can now do with the 'conservation status' facet.\r\n\r\nInvasives are extremely important to the Australian economy and we need a simple mechanism of identifying this class of species in any situation in the ALA. For example, SP Area reports need to list the number of 'invasives' in the area and link to a list of the species.\r\n\r\nThere is no standardized terminology of invasive 'status' but that parallels the differentiation of conservation status between States and Territories. Conclusion: We use whatever 'invasive' information is available to tag any species. People such as Melodie McGeoch are working on this internationally and nationally but we urgently need to expose some form of 'straw man' until the domain gets its act together. The 'straw man' will very likely play a key role in developing an agreed strategy.\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Enhancement", | |
"ID": "511", | |
"Modified": "Apr 27, 2014 22:12:05", | |
"ModifiedTimestamp": "1398636725", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Generate a comprehensive PDF-based Area Report", | |
"Type": "Enhancement", | |
"details": [ | |
"\nA comprehensive Area Report is likely to be one of the most powerful/useful things that we could currently produce. Such as report is beyond the current on-screen report that we currently produce. \r\n\r\nWe have a lot of information about areas (and this is increasing), so it is vital that we integrate this information into a comprehensive PDF-based report that could be used for\r\n\r\n1. Environmental impact assessment\r\n2. Regional, local planning\r\n3. Environmental management and remediation\r\n4. Identifying gaps in ALA data\r\n5. Research\r\n6. State of the Environment Reporting\r\n7. Environmental monitoring\r\n\r\nThe attached file is a mock-up of such a report. It has been produced after discussion with Linda and Natasha. Some components may take time to produce so some form of background and notification strategy may be required. I would anticipate that users will however wait for 5 minutes or so as long as they get feedback on what is happening. Even \"Step 1/20..step 2/20 etc.\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Defect", | |
"ID": "576", | |
"Modified": "Mar 02, 2014 21:50:39", | |
"ModifiedTimestamp": "1393797039", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Surface Geology layer fails in use with MaxEnt (Prediction)", | |
"Type": "Defect", | |
"details": [ | |
"\nPossibly related to #547. User picked detected that when the surface geology layer (a complex 250m layer very similar to dynamic land cover) is used in a Prediction, the system fails. Failure validated: See process/analysis ID: 1392155115716\r\n\r\nPrediction does however work with dynamic land cover so I think it may be that surface geology has not been fully 'processed' into the system (which DLC has).\r\n\r\nUser who detected this issue has been notified (cc support@ala)\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-High, Type-Defect", | |
"ID": "597", | |
"Modified": "Feb 26, 2014 03:13:40", | |
"ModifiedTimestamp": "1393384420", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Conservation status facet not reflecting species status", | |
"Type": "Defect", | |
"details": [ | |
"\nAdd to Map | Species | Mogurnda clivicola\r\n\r\nThis species is listed as \"Vulnerable\" (AU) in the species page but not in the facets.\r\n\r\nState conservation\r\nState conservation status (unprocessed)\r\n\r\nThis seems to imply that a species listed under the EPBC act will not reflect in either of the two conservation status facets? If so, not nice.\r\n\r\nThis issue was raised by a user from SA (via Robyn Lawrence) who was attempting to find out what fish species in SA had a conservation status.\r\n\r\nApparently there are 16 fish species in SA with some conservation status while the ALA reports 2 as far as I can tell. If I use the SP to facet on lifeform=fish, area=SA with coastal zone, conservation=some status I get 2.\r\n\r\nI assume it is a biocache issue.\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-High, Type-Defect", | |
"ID": "650", | |
"Modified": "Jun 09, 2014 07:40:07", | |
"ModifiedTimestamp": "1402299607", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Standardise assertions across all ALA services", | |
"Type": "Defect", | |
"details": [ | |
"\nIn developing the R library (ALA4R) for interfacing with ALA data, inconsistencies in the assertions have been detected. \r\n\r\nThe assertions developed by the ALA are the most significant value-add to the records available - particularly for the research community. 'Data Quality' has remained one of the most significant issues raised by the research community so it is vital that we communicate the assertions in a comprehensive and consistent manner. The intent in ALA4R is to enable users to visualize the assertions associated with a record set. For this to happen, assertions need to be comprehensive and consistent.\r\n\r\nThere are at least three sources of information related to record assertions in the ALA\r\n\r\n1. ", | |
"\r\n2. ", | |
"\r\n3. Downloaded records from spatial portal, biocache, ALA4R etc\r\n\r\nThere needs to be one location where the list of assertions are, and (extremely important), their definitions can be found. This location should be linked to wherever assertions are exposed. There are currently missing assertions from the list in (2) above and others are not defined.\r\n\r\nAssertions need to be a consistently named. At the moment, there are two different sets of names (and maybe more). I'd suggest that the names at ", | |
" be used throughout the systems.\r\n\r\nAs far as I can tell, the assertions appended to downloads are a consistent subset. If it was decided to remove assertions for which ALL records are \"FALSE\" (as was suggested happens by Dave M), fine - but this may conflict (at least by default) with ", | |
". There is a current maximum of 87 assertions so there is probably a case for removal of 'non applicable' assertions from the records downloads to reduce data volume.\r\n\r\nThe attached spreadsheet is a summary of the assertions from the three locations noted above. Highlighted cells in the spreadsheet represent missing information, as far as I can tell - without comprehensive definitions.\r\n\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Defect", | |
"ID": "678", | |
"Modified": "May 26, 2014 02:01:15", | |
"ModifiedTimestamp": "1401069675", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Biocache - view in SP produces zoom and facet issues", | |
"Type": "Defect", | |
"details": [ | |
"\nFrom Margaret Cawsey (and validated by me):\r\n\r\n\"Double barred finch\" in ", | |
"\r\nFilter from ~62K records to 173 by ANWC OZCAM provider\r\nView in SP\r\n\r\n----Errors\r\n\r\n1.Zoom is not full extent of distribution (about 66%)\r\n\r\n2. Facet on Date by decade), lifeform, LGA, state/territory, biogeographic region (whatever that is - and this is another issue!), IBRA, DLC, vegetation type (native and present), month, year, decade, provenance, record issues, associated record - we are getting a HEAP of additional dots on the map that do not have a corresponding class.\r\n\r\nI've put it as an SP issue but recent biocache reindexing may be the issue?\r\n\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Enhancement", | |
"ID": "700", | |
"Modified": "Jun 16, 2014 01:55:37", | |
"ModifiedTimestamp": "1402883737", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Load Layer: Physiographic regions of Australia", | |
"Type": "Enhancement", | |
"details": [ | |
"\nPhysiographic regions of Australia is a high-level base layer useful for defining environmental characteristics, particularly to the freshwater environment.\r\n\r\nIf possible, I would like to have this layer for demos at the Australian Society for Fish Biology and Australian Society for Limnology Congress Darwin 30th June.\r\n\r\nMetadata and data sent to Adam\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Enhancement", | |
"ID": "709", | |
"Modified": "Jun 18, 2014 06:00:31", | |
"ModifiedTimestamp": "1403071231", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Load layer: Ecohydrological classification (Janet Stein)", | |
"Type": "Enhancement", | |
"details": [ | |
"\nThis layer would be extremely useful for the 'freshwater conference' demo (July 1).\r\n\r\nFrom Janet Stein:\r\n\r\nThe adopted 30 group ecohydrological environment classification can be downloaded from ", | |
" - demstreamsv293.zip has a vector representation (shape format) of the stream network with classification group attributed or if you prefer raster formats there is a zipped arc/info workspace (allstdg30cat.zip) containing two rasters of the ecohydrological classification for, respectively, the raster stream network and its sub-catchments.\r\n\r\nLater (probably via BOM geofabric data, but left here for context)-\r\n\r\n(However, the underpinning spatial layers and associated environmental attributes were all updated for the Geofabric and other more recent projects so this data is not current. The other classifications can probably be supplied in the form of a lookup table to link to the stream layer if you would like them as well.) \n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Enhancement", | |
"ID": "715", | |
"Modified": "Jul 08, 2014 05:03:48", | |
"ModifiedTimestamp": "1404795828", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Load Layer: Selected Geofabric layers", | |
"Type": "Enhancement", | |
"details": [ | |
"\nAfter an examination of the available Geofabric layers from BoM, a subset would seem to help with bridging the 'freshwater gap' in the ALA. \r\n\r\nIt would be terrific if some of these could be loaded before next week so as to demo at the freshwater conference in Darwin. Priority layers 36,46,47,64 :|\r\n\r\nData: ", | |
"\r\n\r\n1. 36 ahgf_gwc:AHGFSurficialHydrogeologicUnit (contextual)\r\n2. 38 ahgf_gwc:AHGFAquiferOutcrop (contextual)\r\n3. 39 ahgf_gwc:IGWAquiferSalinity (contextual)\r\n4. 46 ahgf_hrr:AWRADrainageDivision (contextual)\r\n5. 47 ahgf_hrr:RiverRegion (contextual)\r\n6. 48 ahgf_shcarto:Surface_Cartography_2.1 (?? vector)\r\n7. 51 ahgf_shcarto:AHGFWaterbody (contextual 1/0)\r\n8. 53 ahgf_shcarto:AHGFEstuary (contextual 1/0)\r\n9. 63 ahgf_shcarto:AHGFWaterbodyWaterStorage (contextual 1/0)\r\n10. 64 ahgf_shcarto:AHGFNetworkStreamsMajor (?? vector)\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-High, Sandbox, Spatial-Portal, SpatialPortal, Type-Enhancement", | |
"ID": "64", | |
"Modified": "Aug 12, 2013 04:07:21", | |
"ModifiedTimestamp": "1376280441", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Integrate with sandbox", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "BIE, Biocache, Collectory, Priority-High, Type-Enhancement", | |
"ID": "285", | |
"Modified": "Nov 11, 2013 03:59:56", | |
"ModifiedTimestamp": "1384142396", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Image view logging at the collection / institution level", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "422", | |
"Modified": "Jan 24, 2014 03:42:58", | |
"ModifiedTimestamp": "1390534978", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Partition document uploads to avoid a 32k document limit on a single directory", | |
"Type": "Enhancement", | |
"details": [ | |
"\nPartition document uploads to avoid a 32k document limit on a single directory\r\n\r\nWe've hit the 32k inode problem with biocache and BVP and will probably hit it with Fieldcapture/ecodata.\r\nIf we can add document partitioning of the uploaded docs before going live then it'll make life easier.\r\n\r\nSuggest partition by year-month of upload, or something simple.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "AUTH, Priority-High, Type-Defect", | |
"ID": "535", | |
"Modified": "Jan 31, 2014 01:51:59", | |
"ModifiedTimestamp": "1391133119", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "user auth emails are getting blocked by SPAM filters", | |
"Type": "Defect", | |
"details": [ | |
"\nWe have a common ongoing issue with auth that outgoing emails for account activation are blocked by SPAM filters.\r\n\r\nPlease add any recommendations to avoid SPAM filter pitfalls to this issue and we'll makes some changes.\r\n\n" | |
], | |
"project": "AUTH" | |
}, | |
{ | |
"AllLabels": "Alerts, BVP, Priority-High, Type-Enhancement", | |
"ID": "548", | |
"Modified": "Jan 28, 2014 03:26:56", | |
"ModifiedTimestamp": "1390879616", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Switch from email address to using user ID", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "Biocache, ListsTool, Priority-High, Type-Defect", | |
"ID": "605", | |
"Modified": "Mar 13, 2014 00:48:06", | |
"ModifiedTimestamp": "1394671686", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "QID issues for creating alerts from specieslists", | |
"Type": "Defect" | |
}, | |
{ | |
"AllLabels": "Priority-High, SpatialPortal, Type-Defect", | |
"ID": "606", | |
"Modified": "Mar 13, 2014 01:48:45", | |
"ModifiedTimestamp": "1394675325", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "Accepted", | |
"Summary": "Redirect http://spatial-dev.ala.org to spatial.ala.org and setup new dev url", | |
"Type": "Defect", | |
"details": [ | |
"\nWalter Jetz published a link to spatial-dev.ala.org.au in Integrating biodiversity distribution knowledge: toward a global map of life (doi:10.1016/j.tree.2011.09.007)!\r\n\r\nWe need to \r\n\r\n1. Redirect spatial-dev to spatial\r\n2. Setup a new link to the dev system\r\n\r\n\r\n\r\n\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Biocache, ListsTool, Priority-High, Type-Defect", | |
"ID": "258", | |
"Modified": "Oct 02, 2013 22:59:38", | |
"ModifiedTimestamp": "1380754778", | |
"Owner": "moyesyside", | |
"Priority": "High", | |
"Status": "OnDev", | |
"Summary": "Speices list \"View occurrence record\" broken for dr487", | |
"Type": "Defect" | |
}, | |
{ | |
"AllLabels": "Biocache, Hubs, Priority-High, SpatialPortal, Type-Enhancement", | |
"ID": "263", | |
"Modified": "May 22, 2014 00:04:57", | |
"ModifiedTimestamp": "1400717097", | |
"Owner": "nickdos", | |
"Priority": "High", | |
"Status": "Started", | |
"Summary": "ShapeFile export of point data", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-High, Type-Enhancement", | |
"ID": "735", | |
"Modified": "Jul 08, 2014 05:33:51", | |
"ModifiedTimestamp": "1404797631", | |
"Owner": "Sathish.Sathyamoorthy", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Support for multiple project funding sources", | |
"Type": "Enhancement", | |
"details": [ | |
"\nNew doE programmes require projects to be apportioned across multiple funding streams. This is also a requirement of the generalised system as many projects undertaken by organisations involve multiple funding partners.\r\n\r\nA simple multi-row table in the Admin>Project information tab should be adequate for this putpose.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-High, Type-Enhancement", | |
"ID": "212", | |
"Modified": "Aug 09, 2013 04:44:59", | |
"ModifiedTimestamp": "1376023499", | |
"Owner": "snomelf", | |
"Priority": "High", | |
"Status": "New", | |
"Summary": "Link from BVP to expeditions pages in the ALA", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Nov 7, 2012 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 7, 2012 \r\nSee attached file for nature and location of links\r\n1. Front page - Link menu at top\r\n2. Front page - link in Stats area\r\n3. Expedition List Page - next to expedition name\r\n4. Expedition front page - in left nav\r\n5. On Volunteer page \r\n\r\n StatsandALAlinks.pptx 991 KB \u00a0 Download Nov 7, 2012 Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Cc: [email protected]\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Spatial-Portal, SpatialPortal, Type-Task", | |
"ID": "65", | |
"Modified": "Aug 08, 2013 23:28:40", | |
"ModifiedTimestamp": "1376004520", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Add generalized Dissimilairity Modelling to SP", | |
"Type": "Task", | |
"details": [ | |
"\nOriginal Issue - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 22, 2010 \r\nCode and documentation received from Glenn Manion. Slot in integration with the Spatial Portal\r\n Mar 17, 2011 Project Member #1 [email protected] \r\nUpping to HIGH as we need something basic running for meeting with Simon, Glenn, Kristen probably during the week of April 4.\r\n Labels: -Priority-Medium Priority-Critical May 12, 2011 Project Member #2 [email protected] \r\nLowering priority till UI done.\r\n Cc: [email protected] Labels: -Priority-Critical Priority-High May 24, 2011 Project Member #3 [email protected] \r\nStarted\r\n Status: Started Jan 2, 2012 Project Member #4 [email protected] \r\nNow to critical due to NPEI project that must be completed by June 30.\r\n Labels: -Priority-High Priority-Critical Feb 2, 2012 Project Member #5 [email protected] \r\nRan all of Acacia on Tasmanian extent with equal site weight and first 5 test layers and didn't perceive that I got any GDM output other than the input-\r\n\r\n", | |
"\r\n\r\n[DIR] Parent Directory - \r\n[ ] domain.grd 03-Feb-2012 12:52 311 \r\n[ ] domain.gri 03-Feb-2012 12:52 0 \r\n[TXT] gdm_params.txt 03-Feb-2012 12:52 673 \r\n[TXT] species_points.csv 03-Feb-2012 12:52 33K \r\n\r\n Feb 6, 2012 #6 ajay.ranipeta \r\nThere was some code reverted. Process should now generate the species file with Longitude, Latitude, Species_name. \r\n\r\nCurrently working on generating graphs and including them in the metadata file. \r\n Feb 8, 2012 Project Member #7 [email protected] \r\n1. Need to swap over to import/paste assemblage code (which is seems to tap anyway)\r\n\r\n2. Keeps cycling back to step 2 after mapping assemblage. Doesn't get to ask about environmental layers\r\n\r\n3. Restrict mapped species to an area. Seems redundant as the area is defined in step 1? (So the answer is always \"yes\".\r\n\r\n\r\n Mar 1, 2012 #8 ajay.ranipeta \r\nlatest code from Glenn now generates a segmentation fault.\r\n\r\nmetadata and charts should however be done (hopefully) now.\r\n Mar 13, 2012 #9 ajay.ranipeta \r\nIn test.\r\n Status: InTest Mar 14, 2012 Project Member #10 [email protected] \r\nLooking good Ajay! A few comments\r\n\r\n1. After designating layers should \"working...\" be replaced by a progress bar?\r\n\r\n2. GDM options\r\nGenerate quantile from: Data [this is a statement, not an option?]\r\nUse geographic distance as additional predictor: yes no\r\nUse all site pairs\t[this is also a statement as there is no option?]\r\n\r\n3a. Naming prediction layers should default to something like \"My GDM prediction\"\r\n\r\n3b. List of environmental layers is blank even though I selected the best 5. I can't get past Step 4\r\n\r\n\r\n\r\n\r\n\r\n\r\n Status: Started Mar 14, 2012 #11 ajay.ranipeta \r\n1. Leaving it as \"Processing... \", I think. There is really one step which generates the domain grid and figures out the site pairs and should give you the option. I could randomly set it to, say a minute but it should take less than a minute to process\r\n\r\n", | |
"\na) it was meant to be an option, but now a default is set as recommended by Simon/Kristen. Now I've left it there for more as an information for the end users\r\n\r\nb) this is fine.\r\n\r\nc) No, not a statement. You should be able to uncheck the box which gives you more parameters to play with.\r\n\r\n3a/b. Yea, so step 1 didn't really work, which might have not really finished off the whole process. This default layer name should come up as \"My GDM\".\r\n\r\ntesting and fixing the GDM issue now.\r\n Mar 14, 2012 #12 ajay.ranipeta \r\nsomehow whoever updated the GDM code on dev didn't grab the latest from SVN. Have done that now and should all be fine. \r\n\r\ntest again Lee.\r\n Status: InTest Mar 14, 2012 Project Member #13 [email protected] \r\nThanks Ajay: A lot better.\r\n\r\n1. The html looks good, but suggest the file be called gdm.html\r\n\r\n2. ala.properties should be gdmparameters.txt. Not sure how you want to differentiate this from gdm_params.txt\r\n\r\n3. We need the transform grids as layers for further analysis (hover, sampling, scatterplot, classification, prediction). These I guess will just be scaled 0-1 or 0-100. At the moment, there is nothing mapped from the run.\r\n\r\n4. We need a Readme.txt file to describe all the files in the zip, as ever.\r\n\r\n5. Would be good to substitute scientific name for species code in output (e.g., species frequency table)\r\n\r\n6. Name for 'prediction layer' requested but not used?\r\n\r\n\r\n Status: Started Mar 14, 2012 #14 ajay.ranipeta \r\n1. ok\r\n\r\n2. no, i generate the ala.properties so i can keep track of something to help generate the html page.\r\n\r\n3. umm.. \r\n\r\n4. waiting for a final confirmation from Kristen/Simon/Glenn to get back to us about the current implementation and if there are any changes and any final file generations.\r\n\r\n5. I'll need to generate a csv file that provides an index for species code to scientific name/lsid\r\n\r\n6. huh? the file prompted for the download has the layer name set. \r\n Mar 27, 2012 #15 ajay.ranipeta \r\nupdated dev to include the output transformed grids as layer on SP. This will them to be available for:\r\n\r\n- hover tool\r\n- sampling\r\n- other analysis tools\r\n\r\n Mar 27, 2012 #16 ajay.ranipeta \r\n(No comment was entered for this change.)\r\n Status: InTest Apr 1, 2012 Project Member #17 [email protected] \r\nNo output layers mapped at the moment.\r\n Status: Started Apr 3, 2012 #18 ajay.ranipeta \r\n(No comment was entered for this change.)\r\n Status: InTest Apr 3, 2012 Project Member #19 [email protected] \r\nIf Acacia + Eucalyptus are used for Tasmanian extent, GDM step 1 reports 0 records per cell. It used to report a more realistic range.\r\n Status: Started Apr 12, 2012 Project Member #20 [email protected] \r\nThanks Ajay. A lot better. The output transformed layers are all however called \"Transformed null\"\r\n\r\n\r\n Apr 12, 2012 #21 ajay.ranipeta \r\n(No comment was entered for this change.)\r\n Status: InTest Apr 12, 2012 Project Member #22 [email protected] \r\nLooks great! I'll get Kristen to have a play now.\r\n\r\n Apr 19, 2012 Project Member #23 [email protected] \r\nKristen (April 19): Summary \u2013 issues with running more than default number of site pairs, classification of transformed grids didn\u2019t work, additional outputs needed in zip file, HTML file needs a bit more work. \r\n\r\n1.\t\u201crecords per cell\u201d \u2013 this may be explained when we have the help files (when we write them) but intuitively \u201crecords\u201d to me means the number of species by locations within a grid cell (I\u2019m assuming this is a 1km grid cell). I think it would be more transparent to label this \u201ctaxa per cell\u201d (do we mean species? are these matched-species, is there an option to choose matched species? it is important to know what the taxonomic unit is for GDM). I\u2019m assuming the table represents the number of taxa per cell, rather than the number of records per cell. We had this conversation before and checked with Glenn. Even if Glenn uses the label \u201crecords per cell\u201d and assuming the data is actually \u201ctaxa per cell\u201d we should present the label as \u201ctaxa per cell\u201d. \r\n2.\t \u201cSelect a threshold to help generate the site pairs\u201d this should be changed to something like: \u201cSelect the minimum number of taxa in a single grid-cell representing an assemblage to include\u201d. The choice of threshold is designed to improve the quality of the data toward a \u201cpresence-absence\u201d sample by removing grid cell (sites) from consideration, not so much to help with generating the site-pairs, but does reduce the number of sites considered in generating site-pairs. I used a threshold of \u20188\u2019. \r\n3.\tThe bar for using all site pairs should also show the % site pairs (if easy to calculate on the fly)\r\n4.\tThe button for \u201cuse all site pairs\u201d \u2013 should say \u201cchoose the number of site pairs to use\u201d or \u201cuse default number of site pairs\u201d. I entered a number but it is not clear what would happen if I switched the button on or left it off. Are the button and bar interchangeable \u2013 one or the other, does one supersede the other? The default appears to be 1% (what was the rationale for the default?). The default should probably be set around 1 million site pairs or the number of available site pairs whichever is the lowest. For my random example the total site pairs is 4096000. The default is 40960. This wouldn\u2019t be a big enough sample to model, so I chose 1045070. My analysis is for Corymbia with the 5 standard predictors. I choose weight by number of species. \r\n5.\tProcessing: after a short time a message comes back saying the server is temporarily out of services, and stops the analysis although one has to physically close the window. Seems to say something about a bad gateway\u2026(is this a problem at my end related to my network and internet settings or software \u2013 I\u2019m using Google Chrome - or at the ALA server end?) \r\n6.\tI then had to start again. Perhaps the prelim analysis could be kept and become a set of assemblage points in then I could start again where I left off and try a different number of site pairs? This time I try 539391 site-pairs, and note that the bar is not present until I switch off the \u201cdefault\u201d\u2026 again the server out of service message came up\u2026 and the result below appeared\r\n7.\tGDM processing can take a while, it might be better if it went into the background on the server and returned the user to the ALA interface and then produced an email or pop-up when the processing is complete? \r\n8.\tThe user may undertake several iterations with GDM in order to find the best set of variables to include in the model. Typically, I iterate in using the fitting function of the model and when I\u2019m satisfied I produce the transformed grids. \r\n9.\tI try again, this time using the default number of site pairs\u2026.this time it worked\u2026and I have a look through the outputs, the transformed grid are also available for further analysis (or modelling)\r\n10.\tI now create a classification based on my transformed predictors using 20 groups\u2026but I received a failed message \u2013 in working through the steps of the classification, on the last page, the layer set is not listed? Is this an indicator of why the classification is not working with the transformed grids? I tried twice and the classification step failed each time\u2026\r\nHTTP Status 404 - /webportal//error/HTTP_NOT_FOUND.html.var\r\n\r\n Apr 19, 2012 #24 ajay.ranipeta \r\nKristen (April 19): Metadata info\r\n\r\nComments on HTML report:\r\n \r\nUnder \u201cyour options\u201d at the top of the HTML file need to include additional information about the parameters used in the analysis, please include:\r\n- Assemblage: (e.g. Corymbia) (plus include the records for the assemblage in the download; add the assemblage to the map in the spatial portal) I was able to create my own download but have no idea what the taxonomic unit in the GDM analysis is. Nor do I know what the list of species aggregated by grid cell is?\r\n\r\n- Number of unique taxa: # (include a list of taxa that can be related to the \u201ccode\u201d in the species_points.csv file \u2013 we\u2019ve talked through this before, the need to be able to identify the taxa used in the analysis \u2013 exactly what were these.)\r\n\r\n- Taxa resolution: subtaxa (i.e., is the cut-point of the taxa set at matched species or are all levels of taxa included?)\r\n\r\n- Grid-cell resolution: 0.01\r\n\r\n- Minimum number of taxa per grid cell: # (e.g. 8) (This is described as the cut point in GDM_parameters.txt)\r\n\r\n- Number of grid cells with taxa included in the model: #\r\n\r\n- Total number of site-pairs: # (e.g., 4096000)\r\n\r\n- Number of site-pairs used in the analysis: # (e.g. 40960)\r\n\r\n- Number of predictors used in the analysis: # (e.g. 5)\r\n\r\n- Number of I-splines per predictor: 3 (this is a default that is hard wired into this version of GDM)\r\n\r\n \r\nCreate a new section: \u201cModel Summary\u201d (this can be drawn from the file gdm_parameters.txt)\r\n- Intercept=0.612189\r\n\r\n- Null Deviance=70125.728738\r\n\r\n- GDM Deviance=54905.896804\r\n\r\n- Deviance Explained=21.703635\r\n\r\n- All Coefficients Summed=12.193876\r\n\r\n \r\nCharts and text:\r\n- The cut-point.csv table could be presented first along with explanatory text so that users understand how to apply this parameter.\r\n\r\n- Observed versus predicted compositional dissimilarity (raw data plot): x-axis should not be labeled after a value of 1.0 (predicted values do not extend this far) and red line should end at a value of 1.0\r\n\r\n- \u201csite pairs\u201d or \u201csite-pairs\u201d inconsistent \u2013 I would prefer we used hyphenated \u201csite-pairs\u201d\r\n\r\n- Observed compositional dissimilarity vs predicted ecological distance (link function applied to the raw data plot): \u201cThe line represents the perfect 1:1 fit.\u201d Not red curve and change to \u201cThe red curve represents the perfect 1:1 fit.\u201d\r\n\r\n- Instead of \u201cThe scatter of points signifies noise in the relationship between the response and predictor variables.\u201d Say \u201cThe scatter of points signifies residual variation and noise in the relationship between the response and predictor variables.\u201d Not all of the scatter will be noise, some may be systematically correlated with variables not included in the model.\r\n\r\n- The plots of each predictor variable are not correctly linked into the HTML file\u2026and links to the full plots as well as thumbnails would be handy \u2013 same as for maxent, from memory I think you can open the full plots by clicking on the thumb nails\r\n\r\n- Data list \u2013 need to include a list at the end of the HTML file describing each of the datasets provided in the zip file and what they mean. If Ajay could start with a list, I could draft the commentary and Glenn could check this is right (see attached spreadsheet for starters). I guess this is the objective of the \u201creadme.html\u201d which is presently blank.\r\n\r\n- Need lookup table relating \u201cspecies code\u201d to the actual taxon name used in the GDM analysis that would enable these to be matched to an ALA identifier in the data downloaded for an assemblage\r\n\r\n- Need a lookup table relating \u201cEnvGrid#\u201d to the layer name. This can be inferred from the gdm_params.txt\r\n\r\n May 27, 2012 Project Member #25 [email protected] \r\nKristen: I think it would be worth making step 4 GDM Options that produces the summary of species available with an Analysis ID. If the analysis fails (which it almost always does for me because I pick too large an extent or too many site pairs), one has to go back to scratch. If the entries can be saved at Step 4, then one can make a small modification to the # site pairs and try again? Better still, run the GDM as a background job\u2026so that most analyses produce a result. \r\n\r\nLee: Ajay is currently working on background processing (#722).\r\n Status: Started Aug 21, 2012 Project Member #26 moyesyside \r\nLee - to my knowledge this is all done and in production. Is this correct?\r\n Owner: [email protected] Cc: [email protected] [email protected] Aug 21, 2012 Project Member #27 [email protected] \r\nNo, GDM isn't complete. Kristen and I still have to discuss what may be required to at least tidy GDM up. Kristen has her head down on NPEI and probably a heap of other work so I'm leaving it till she pops her head up. Needless to say, I'm busier than I'd like to be at this stage as well.\r\n Cc: [email protected] moyesyside Labels: -Priority-Critical Priority-High Jul 8, 2013 Project Member #28 [email protected] \r\nLowering (Medium) until we can get some of Kristen's time. Issues:\r\n\r\n1. GDM help review/edit\r\n2. GDM case study\r\n\r\nUpdates to GDM will need to wait for higher priority issues to be addressed.\r\n Owner: [email protected] Cc: [email protected] [email protected] Labels: -Type-Enhancement -Priority-High Type-Task Priority-Medium\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, SpatialPortal, Type-Defect", | |
"ID": "500", | |
"Modified": "Jul 17, 2014 05:43:48", | |
"ModifiedTimestamp": "1405575828", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Analysis tools cannot handle large grids", | |
"Type": "Defect", | |
"details": [ | |
"\nThis problem was discovered when loading a large grid file as part of the fieldcapture work.\r\n\r\nSome of the analysis tools make the assumption that all grid files can be read into byte arrays. These tools fail when reading a grid file containing a number of bytes larger than the maximum array size in Java.\r\n\r\nThis problem occurs in the GridLegend tool and the Intersect service, but it may occur elsewhere.\r\n\r\nI have fixed the problem in the Bil2Diva tool by iterating over grid files one megabyte at time.\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Spatial-Portal, SpatialPortal, Type-Defect", | |
"ID": "60", | |
"Modified": "Jun 19, 2014 00:19:50", | |
"ModifiedTimestamp": "1403137190", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Re-process Surficial geology", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], May 29, 2012 \r\nNeed to source a gridded version of this dataset - the only copy I can find of the raw data consists of extremely large shape files.\r\n\r\nThe layer then needs to be re-loaded using the GridClassBuilder\r\n\r\n\r\n Jun 18, 2012 Project Member #1 [email protected] \r\nEmailed Leo Lymburner to see if he can get a copy in grid format.\r\n Labels: -Priority-Medium Priority-High Jun 6, 2013 Project Member #2 [email protected] \r\nHi Lee,\r\n\r\nThis one has fallen through the cracks - did you ever hear back about it? We had also discussed this with Kristen. Is it still a high priority?\r\n\r\nCheers,\r\nChris\r\n Cc: [email protected] moyesyside Jun 6, 2013 Project Member #3 [email protected] \r\nI've emailed Leo again about this. If no response, I'll ask Kristen as I know she will have this as a soil surrogate, but format - who knows.\r\n Jul 8, 2013 Project Member #4 [email protected] \r\nKristen Williams has these data and could supply a 250m gridded version. Please pursue, via Miles?\r\n\r\nNOTE: The reason the gridded data is needed is for processing for Tabulation and I suspect, Add to Map | Areas | Gazetteer polygon.\r\n\r\nRemains a high priority as the layer is available to map but not to use in analyses. Inconsistent. Handed to Chris.\r\n Owner: [email protected] Cc: [email protected] [email protected]\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Layers, Priority-Medium, SpatialPortal, Type-Enhancement", | |
"ID": "68", | |
"Modified": "Jun 16, 2014 06:28:12", | |
"ModifiedTimestamp": "1402900092", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Load layer: Global Administrative Boundaries V2", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, SpatialPortal, Type-Enhancement", | |
"ID": "697", | |
"Modified": "Jun 13, 2014 01:33:27", | |
"ModifiedTimestamp": "1402623207", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Rationalise i18n mappings", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "LayerServices, Priority-Medium, Type-Defect", | |
"ID": "730", | |
"Modified": "Jul 04, 2014 06:45:14", | |
"ModifiedTimestamp": "1404456314", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Layer-service still using layer.properties in WEB-INF/classes", | |
"Type": "Defect", | |
"details": [ | |
"\nLayer-service still using layer.properties in WEB-INF/classes as opposed to solely relying on external config,\r\n\r\nThis was the problem on dev. \n" | |
], | |
"project": "LayerServices" | |
}, | |
{ | |
"AllLabels": "Layers, Priority-Medium, SpatialPortal, Type-Enhancement", | |
"ID": "67", | |
"Modified": "May 29, 2014 06:46:05", | |
"ModifiedTimestamp": "1401345965", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Load Layer: New Weathering Intensity Index (WII)", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Spatial-Portal, SpatialPortal, Type-Defect", | |
"ID": "70", | |
"Modified": "Jul 07, 2014 23:35:49", | |
"ModifiedTimestamp": "1404776149", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Export of own data fails", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Jul 2, 2013 \r\nSpatial Portal. When exporting own data, if a layer is not chosen, export fails. MESSAGE: Unknown error\r\n\r\n", | |
"\n1. Import own dataset\r\nAdd to Map - Species - Import points\r\n2. Export that dataset\r\nExport - Point Sample\r\nArea=current extent\r\nSelect species=MyData\r\nSampling - DO NOT CHOOSE A LAYER (if you choose a layer, this export will not fail)\r\n3. Message=Unknown error\r\n\r\nWhat is the expected output? \r\nDownload of my own data\r\n\r\nWhat do you see instead?\r\nError message, Message=Unknown error\r\n\r\nWhat version of the product are you using? On what operating system?\r\nFF21 on Win7\r\n\r\nPlease provide any additional information below.\r\nProbably not a serious error. Why would anyone want to export their own data without adding any layers, etc?\r\nHowever, I had a problem with the operation of the SP and was trying to check whether it was my data (had ALA corrupted it) or something else.\r\n Jul 8, 2013 Project Member #1 [email protected] \r\nVerified error. Thanks John.\r\n\r\nWe need to at least produce a reasonable message that says something like \"No sampled layers have been selected\" when an \"Export | Point sample\" is attempted on an \"Import | Points\" - illogical as it is.\r\n Status: Accepted Owner: [email protected] Cc: [email protected] moyesyside [email protected]\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Spatial-Portal, SpatialPortal, Type-Enhancement", | |
"ID": "71", | |
"Modified": "May 05, 2014 07:02:47", | |
"ModifiedTimestamp": "1399273367", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "iPad issues", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Oct 16, 2011 \r\nRan a broad test on Prod using the iPad and here are the issues I found. I realize that it is probably not designed for the type of heavy browser load the SP can involve-\r\n\r\n1. Difficulties in tapping on small icons such as remove menu (LHS) and restore menu\r\n\r\n2. Next button on species upload won't activate (not selectable) \r\n\r\n3. No support for map or scatterplot digitizing. Unsure how we could address this.\r\n\r\n4. Sampling seems to cycle through steps 1-3\r\n\r\n5. Sliders don't work that well. What seems to work is to click on slider position.\r\n\r\n6. No point select for Hover Tool support\r\n Nov 22, 2011 #1 [email protected] \r\nReassigning to Ajay for consideration.\r\n Owner: ajay.ranipeta Feb 22, 2012 Project Member #2 [email protected] \r\n Issue 896 has been merged into this issue.\r\n Cc: [email protected] [email protected] Apr 11, 2012 Project Member #3 [email protected] \r\nFix for main menu now seems to work fine. Thanks Adam.\r\n\r\nStill odd 'selection' function occurs when using auto-completes.\r\n Status: Started Apr 25, 2012 Project Member #4 [email protected] \r\n(No comment was entered for this change.)\r\n Owner: [email protected] Cc: [email protected] -ajay.ranipeta Labels: -Priority-Medium Priority-Critical Jun 5, 2012 Project Member #5 [email protected] \r\nLowered\r\n Labels: -Priority-Critical Priority-Low Jul 10, 2013 Project Member #6 [email protected] \r\nReassigning and to Medium. Given the rise of the tablet, this is an issue that needs to be at least evaluated in the next 3 months. \r\n\r\nAdam did some work-arounds on species selections that worked well, but at this stage, I have no idea how tricky some of the 6 issues above would be.\r\n Owner: [email protected] Cc: moyesyside Labels: -Priority-Low Priority-Medium\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Spatial-Portal, SpatialPortal, Type-Enhancement", | |
"ID": "77", | |
"Modified": "May 05, 2014 03:55:11", | |
"ModifiedTimestamp": "1399262111", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Basic scatterplot web service", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Jun 21, 2012 \r\nIt would be extremely useful to have a basic scatterplot web service. Supply species and 2 layers and return image.\r\n\r\nAlso add to /ws doco\r\n Dec 3, 2012 Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Owner: moyesyside Cc: [email protected] Labels: -Priority-Critical Priority-Medium\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, SpatialPortal, Type-Enhancement", | |
"ID": "300", | |
"Modified": "Jun 20, 2014 02:11:52", | |
"ModifiedTimestamp": "1403230312", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Load layer: Aqueduct Water risk layers (world extent)", | |
"Type": "Enhancement", | |
"details": [ | |
"\nStephanie ran across ", | |
" and after a look at the data, I believe these layers are well worth getting into the Atlas. Data/metadata at the above URL.\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, SpatialPortal, Type-Enhancement", | |
"ID": "420", | |
"Modified": "Apr 03, 2014 03:45:17", | |
"ModifiedTimestamp": "1396496717", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Facets for Datasets and Data Providers list codes instead of names", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, SpatialPortal, Type-Defect", | |
"ID": "588", | |
"Modified": "May 21, 2014 01:42:12", | |
"ModifiedTimestamp": "1400636532", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Remove the appended spatial layers from the points download", | |
"Type": "Defect", | |
"details": [ | |
"\nReported by Catherine Noble.\r\n\r\nI can't see the logic in routinely appending the values of the spatial layers \"Country - parsed\", \"IBRA Region - parsed\", \"IMCRA Region - parsed\", \" State - parsed\" and \"Local Government Area - parsed\" to the points download. Can these be removed?\r\n\r\nIn the SP, users can select whatever layers they want sampled - and as there is no notification of the routinely appended values, they could be doubly downloaded.\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Layers, Priority-Medium, Spatial-Portal, SpatialPortal, Type-Task", | |
"ID": "66", | |
"Modified": "May 27, 2014 08:03:37", | |
"ModifiedTimestamp": "1401177817", | |
"Owner": "adam.collins832", | |
"Priority": "Medium", | |
"Status": "Blocked", | |
"Summary": "Load layer: Beards Province data of WA", | |
"Type": "Task" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Sightings, Type-Defect", | |
"ID": "241", | |
"Modified": "Aug 18, 2013 23:13:23", | |
"ModifiedTimestamp": "1376867603", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Failed uploads should produce validation error in sightings app.", | |
"Type": "Defect", | |
"details": [ | |
"\nIf an upload of an image fails the failed image file name is still submitted to the server which results in a 404 error when the fielddata app attempts to download the image from the sightings app.\r\n\r\nWe should probably prevent submission until the failed image is re-uploaded or removed from the set.\n" | |
], | |
"project": "Sightings" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Sightings, Type-Defect", | |
"ID": "242", | |
"Modified": "Aug 18, 2013 23:15:26", | |
"ModifiedTimestamp": "1376867726", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Image file names with ',' characters cause errors in the sightings app", | |
"Type": "Defect", | |
"details": [ | |
"\nTo reproduce, attach an image with a ',' in the file name and submit. \r\nThe attach operation works correctly, however the JSON message splits the filename at the comma(s) resulting in an error when the sighting is submitted.\n" | |
], | |
"project": "Sightings" | |
}, | |
{ | |
"AllLabels": "OzAtlasAndroid, Priority-Medium, Type-Enhancement", | |
"ID": "243", | |
"Modified": "Aug 18, 2013 23:42:16", | |
"ModifiedTimestamp": "1376869336", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Add species page list on species profile", | |
"Type": "Enhancement", | |
"details": [ | |
"\nRequested by John La Salle:\r\nAdd a link to the full Atlas species page in the Android app on a species page.\r\nThis would startup the browser on the Android device.\n" | |
], | |
"project": "OzAtlasAndroid" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "280", | |
"Modified": "Jul 17, 2014 05:45:05", | |
"ModifiedTimestamp": "1405575905", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "FieldCapture - Unexpected responses to actions rather than faults", | |
"Type": "Defect", | |
"details": [ | |
"\nExample #1\r\nIn the project tab (not logged in), I click on 'Increasing community capacity to manage ecologically sensitive landcare sites' project to expand and then click on 'show on map' and nothing happens. Expected it to automatically show me the map with the dot. Found out it did zoom to that location in the map tab, but it was hidden so I didn't realise. I was expecting it to switch tabs to show me the location so I knew it was working. This happened for all projects tested.\r\n\r\nExample #2\r\nWhen selecting the 'view project page' from the expanded project details in the project list tab, I expected it to open in and switch to another tab so I didn't lose my place.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "372", | |
"Modified": "Jul 17, 2014 05:44:30", | |
"ModifiedTimestamp": "1405575870", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "New activity type categories needed", | |
"Type": "Enhancement", | |
"details": [ | |
"\nAdditional activity type categories are required to enable more appropriate categorisation of activities in the select list and better usability as the list of activity types grow. Additional activity types needed at this stage are:\r\n General\r\n Monitoring Activities\r\n Biological Surveys\r\n\r\nThe name of the current \"Activities\" category should also change to \"Works Activities\".\r\n\r\nIn addition, the sorting of activities within each category should default to ascending alphabetic.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "388", | |
"Modified": "Jul 17, 2014 05:44:48", | |
"ModifiedTimestamp": "1405575888", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Mandatory field marker often wrapping to a new line", | |
"Type": "Defect", | |
"details": [ | |
"\nSee ", | |
"\r\n\r\nPotentially should be before the help marker as well?\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "459", | |
"Modified": "Jul 17, 2014 05:45:35", | |
"ModifiedTimestamp": "1405575935", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Enhancements to the project audit search", | |
"Type": "Enhancement", | |
"details": [ | |
"\nBecause grant ids are not unique it would be handy to be able to search for a project by guid or external id.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "468", | |
"Modified": "Dec 17, 2013 22:41:02", | |
"ModifiedTimestamp": "1387320062", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Project stage field not populated in activity header.", | |
"Type": "Defect", | |
"details": [ | |
"\nAs the stage is determined dynamically on the activity page, the easiest thing to do is remove this from the page.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "477", | |
"Modified": "Dec 18, 2013 23:21:37", | |
"ModifiedTimestamp": "1387408897", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Allow checkboxes for multiple selection on the \"show more\" filter option on home page facets", | |
"Type": "Enhancement", | |
"details": [ | |
"\nThere is often a need to be able to select multiple options as filters within a facet class, particularly for things like Organisation where differences in spelling, capitalisation and punctuation result in multiple entries for the same organisation (eg. Northern Rivers CMA and Northern Rivers Catchment Management Authority)\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Sightings, Type-Defect", | |
"ID": "515", | |
"Modified": "Jan 13, 2014 22:38:50", | |
"ModifiedTimestamp": "1389652730", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Permanent retry loop for sightings that are added then deleted quickly", | |
"Type": "Defect", | |
"details": [ | |
"\nWhen submitting a sighting for testing purposes, I often will delete it quickly.\r\nIt appears that what happens in this case is that the delete operation completes before the job that syncs the sighting to ALA can run. The job then gets stuck attempting to query the record (which no longer exists).\r\nProbably the delete operation should delete any outstanding create/update jobs or the create/update job has to handle the case where the sighting record no longer exists.\n" | |
], | |
"project": "Sightings" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "553", | |
"Modified": "Feb 04, 2014 03:13:33", | |
"ModifiedTimestamp": "1391483613", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Adjustment to data model for sites", | |
"Type": "Enhancement", | |
"details": [ | |
"\nTo support new requirements of GER and NRM regional planning the following adjustments to the sites data model are required:\r\n1) Replace the current list values for site type with the following:\r\n Asset - National, Asset - Regional, Asset - Local, Event location, Works area - Generalised, Works area - Specific, Project area (general), Other\r\n [NB. Any existing site types in MERIT will either be classed as \"Works area - Generalised\" or \"Project area (general)\", with the project areas being bulk loaded with the string \"Project area for ....\" as the site name.]\r\n\r\n2) Add new fields as follows:\r\n (a) Community/Social values (multi-select + long text)\r\n (b) Environmental values (multi-select + long text)\r\n (c) Economic values (multi-select + long text)\r\n (d) Threats (multi-select + long text)\r\n Multi-select values for these TBA\r\n Search index to also include content from all of these new fields\r\n\r\n3) Change \"Notes\" label to \"Notes and Keywords\"\r\n\r\n\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "554", | |
"Modified": "Feb 04, 2014 03:29:24", | |
"ModifiedTimestamp": "1391484564", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Auto-calculate area for sites", | |
"Type": "Enhancement", | |
"details": [ | |
"\nShould dynamically calculate and auto-populate the area field when sites area created. \r\n\r\nFor polygons - area (Ha) contained within a valid regular polygon of 3 or more verticies\r\n\r\nFor points - area = 1m2 (0.0001 ha) centred at the coordinate specified.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "557", | |
"Modified": "Feb 05, 2014 06:28:44", | |
"ModifiedTimestamp": "1391581724", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Change behaviour for deferring or cancelling an activity", | |
"Type": "Enhancement", | |
"details": [ | |
"\nRequest from DoE.\r\nWhen someone selects deferred or cancelled we need a box to come up saying \"you must contact your grant manager to gain approval\", and allow the grant recipient to shift the activity to a subsequent stage.\r\n\r\nComment - PB 5/2/14\r\nProbably difficult and overly complicated to try inserting a conditional step into the workflow. Maybe the best and easiest way to deal with this would be to add the requested words to the top of the pop-up message (in different colour and/or bolded), plus something to the effect that the grant manager may not approve the report if this is not done.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "558", | |
"Modified": "Feb 12, 2014 05:03:10", | |
"ModifiedTimestamp": "1392181390", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Email notifications on MERI plan submission, acceptance and rejection required", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE request #17\r\nMERIT to send a project submission email to grant manager once grant recipient submits report.\r\n\r\n\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "566", | |
"Modified": "Feb 06, 2014 01:25:57", | |
"ModifiedTimestamp": "1391649957", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Usability improvements for audit tracking on projects", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE requirement #39\r\nInclude audit/tracking function \r\n\r\nComments - PB 6/2/14\r\nThe current audit feature is difficult to use and to hard to interpret what has been changed on a project between approval points. Gran managers are particularly keen for this feature to be enhanced.\r\n\r\nRequirement details TBC, but starting with a better project search capability and a more visual way of seeing what was changed, would be a start. \n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "575", | |
"Modified": "Feb 11, 2014 06:36:54", | |
"ModifiedTimestamp": "1392100614", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Make editable pre-populated result from NVIS spatial dataset in sites", | |
"Type": "Defect", | |
"details": [ | |
"\nIn some cases the NVIS dataset will be too coarse for local application at site level.\r\n\r\nPre-populating the result as per current behaviour should continue, but it should be editable by the user (via select list) to enable a more refined local classification for a site.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "579", | |
"Modified": "Feb 13, 2014 00:45:02", | |
"ModifiedTimestamp": "1392252302", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Allow sites to be created from context of an activity", | |
"Type": "Enhancement", | |
"details": [ | |
"\nUnless sites have already been created for a project, the current UI relationship between activities and sites is cumbersome and unintuitive (at least from the context of an activity) - ie. you can't create a site from within the context of an activity. You have to navigate away from the activity to the sites tab, create the site and then return to the activity to associate it.\r\n\r\nThis enhancement (shown in the attached image) would create a much more intuitive relationship between activity and site, allowing for a site to either be selected from an existing list (as per current behaviour), or created from within the context of an activity, returning to the activity and populating the site selector after it has been created.\r\n\r\nNote however that bulk shape upload functionality would be inappropriate in this context.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "580", | |
"Modified": "Feb 13, 2014 00:57:45", | |
"ModifiedTimestamp": "1392253065", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "DO%sat calculation in Water Quality Measurements output", | |
"Type": "Enhancement", | |
"details": [ | |
"\nAdd algorithm to auto-calculate and populate the \"dissolved oxygen (% sat)\" field in the \"Water Quality Measurements\" output according to the following (from BDRS:NSW Waterwatch:water quality survey). Note that the \"dissolved oxygen (% sat)\" field should not be editable.\r\n\r\n/* Synopsis\r\n\r\n\tOxygenSaturation.setSaturationHandlers('#saturation', '#tempC', '#dox')\r\n\r\n\t- or (before object creation, e.g. inside a BDRS form) -\r\n\r\n\t(function(OxygenSaturation, undefined) {\r\n\t\tOxygenSaturation.autorun = {\r\n\t\t\t'sat': '#attribute_7719',\r\n\t\t\t'tmp': '#attribute_7711',\r\n\t\t\t'dox': '#attribute_7718'\r\n\t\t};\r\n\t})(window.OxygenSaturation = window.OxygenSaturation || {});\r\n\r\n\r\n Description\r\n\r\n\tCalculate the disolved oxygen percent-saturation using the water\r\n\ttemperature and disolved oxygen measure (mg/l). Based on a\r\n\tspreadsheet from Ingrid Berthold (via Peter B).\r\n\r\n\tjQuery handlers are created to update the %sat when the temp and\r\n\toxygen fields are changed. The %sat field is also made read-only.\r\n\r\n\tIf the dictionary `OxygenSaturation.autorun` is defined, then the handlers\r\n\twill automatically be allocated to the form fields named by the\r\n\tdictionary. This is to cope when this file is included AFTER we need it.\r\n\tThe \"calling\" code will create the `autorun` dictionary and it will be\r\n\tused to initialise jQuery when this code is executed.\r\n\r\n\tAlso see ", | |
"\r\n\r\n Copyright\r\n\r\n Copyright (c) 2014 by CSIRO, Australia. All rights reserved.\r\n*/\r\n\r\n// Wrap code in a namespace: OxygenSaturation.*\r\n\r\n(function ( OxygenSaturation, undefined )\r\n{\r\n // hold input field IDs for %sat calculation change handlers\r\n var formIds = {}; // sat, tmp, dox\r\n\r\n /*\r\n Convert the temperature and disolved oxygen into the saturation.\r\n\r\n Input is string (or float) values, output is an int.\r\n (private)\r\n */\r\n function calcSaturation(temperature, disolved_oxygen)\r\n {\r\n \t/*\r\n \tArray index [0..45] is Temperature, value is %saturation multiplyer\r\n \t */\r\n \tvar saturation_factor = [\r\n \t14.62,\t// 0C\r\n \t14.22,\r\n \t13.83,\r\n \t13.46,\r\n \t13.11,\r\n \t12.77,\r\n \t12.45,\r\n \t12.14,\r\n \t11.84,\r\n \t11.56,\r\n \t11.29,\t// 10C\r\n \t11.03,\r\n \t10.78,\r\n \t10.54,\r\n \t10.31,\r\n \t10.08,\r\n \t9.87,\r\n \t9.67,\r\n \t9.47,\r\n \t9.28,\r\n \t9.09,\t// 20C\r\n \t8.92,\r\n \t8.72,\r\n \t8.58,\r\n \t8.42,\r\n \t8.26,\r\n \t8.11,\r\n \t7.97,\r\n \t7.83,\r\n \t7.69,\r\n \t7.56,\t// 30C\r\n \t7.43,\r\n \t7.31,\r\n \t7.18,\r\n \t7.07,\r\n \t6.95,\r\n \t6.84,\r\n \t6.73,\r\n \t6.62,\r\n \t6.52,\r\n \t6.41,\t// 40C\r\n \t6.31,\r\n \t6.21,\r\n \t6.12,\r\n \t6.02,\r\n \t5.93\t// 45C\r\n \t] ;\r\n\r\n \t// convert string args...\r\n \tvar tmp = Math.round(parseFloat(temperature));\r\n \tvar dox = parseFloat(disolved_oxygen);\r\n \tvar saturation = 0;\r\n\r\n \tif ( isNaN(tmp) || isNaN(dox) )\r\n \t{\r\n \t\tsaturation = ''; // TODO: value error values (or blank?)\r\n \t}\r\n \telse if ( tmp < 0 || tmp >= saturation_factor.length )\r\n \t{\r\n \t\tsaturation = '';\r\n \t}\r\n \telse\r\n \t{\r\n \t\tsaturation = Math.round(dox / saturation_factor[tmp] * 100);\r\n \t}\r\n\r\n \treturn saturation;\r\n }\r\n\r\n /*\r\n Perform the calculation on two form fields, storing the result in a third.\r\n (private)\r\n */\r\n function setSaturation(keys)\r\n {\r\n \tvar t = $( keys.tmp ).val();\r\n \tvar d = $( keys.dox ).val();\r\n \t$( keys.sat ).val( calcSaturation(t,d) );\r\n }\r\n\r\n\t/*\r\n\tInit the jQuery handlers.\r\n\t(private)\r\n\t */\r\n function setHandlers(keys)\r\n\t{\r\n\t\tformIds = keys;\r\n\r\n\t\t// make the %saturation field read-only\r\n\t\t$(formIds.sat).attr('readonly', 'readonly');\r\n\r\n\t\t// set change handler for the temperature and disolved oxygen fields\r\n\t\t$(formIds.tmp).change( function()\r\n\t\t\t\t{\r\n\t\t\t\t\tsetSaturation(formIds);\r\n\t\t\t\t}\r\n\t\t);\r\n\r\n\t\t$(formIds.dox).change( function()\r\n\t\t\t\t{\r\n\t\t\t\t\tsetSaturation(formIds);\r\n\t\t\t\t}\r\n\t\t);\r\n\t}\r\n\r\n /*\r\n Set the jQuery handlers to calc & store the saturation when the input fields change.\r\n (public)\r\n */\r\n OxygenSaturation.setSaturationHandlers = function(saturation_id, temperature_id, disolved_oxygen_id)\r\n {\r\n \tsetHandlers( {\r\n \t\tsat : saturation_id,\r\n \t\ttmp : temperature_id,\r\n \t\tdox : disolved_oxygen_id\r\n \t} );\r\n }\r\n\r\n console.log('Init OxygenSaturation');\r\n\r\n /* Automatically set the handlers? */\r\n if (typeof OxygenSaturation.autorun === 'object')\r\n {\r\n \tconsole.log('Oxygen sat: '+OxygenSaturation.autorun.sat);\r\n \tsetHandlers(OxygenSaturation.autorun);\r\n }\r\n\r\n // check to evaluate whether 'OxygenSaturation' exists in the global OxygenSaturation -\r\n // if not, assign window.OxygenSaturation an object literal\r\n})(window.OxygenSaturation = window.OxygenSaturation || {});\r\n\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "592", | |
"Modified": "Feb 21, 2014 01:26:49", | |
"ModifiedTimestamp": "1392946009", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "mismatched brackets in search term results in 500 error", | |
"Type": "Defect", | |
"details": [ | |
"\nTo reproduce enter \"b)\" into the search bar and press search.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "660", | |
"Modified": "May 02, 2014 05:47:21", | |
"ModifiedTimestamp": "1399009641", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "\\ or \" characters in search field result in error.", | |
"Type": "Defect", | |
"details": [ | |
"\nescaped quotes work correctly, mismatched quotes or trailing \\ causes an error.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "733", | |
"Modified": "Jul 08, 2014 06:45:49", | |
"ModifiedTimestamp": "1404801949", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Implement different styling colours between DEV, TEST and PROD environments", | |
"Type": "Enhancement", | |
"details": [ | |
"\nWith implementation of the Demonstrator project in the test environment, some users are finding it difficult to differentiate between the PROD and TEST environments. \r\n\r\nDoE has requested that we change the style colours in TEST to make it distinctly different from PROD.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "736", | |
"Modified": "Jul 06, 2014 04:17:05", | |
"ModifiedTimestamp": "1404620225", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Provide ability to associate 0-many sites with one activity", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE has requested this capability to provide more accurate geotagging of data for the multi-event/multi-action activities.\r\n\r\nNeeds carefult thought as to how to implement to ensure that usability and data entry efficiency are maximised and not compromised at all. It is also currently unclear as to where the process efficiency gains will be achieved for users in this model.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "737", | |
"Modified": "Jul 06, 2014 04:07:43", | |
"ModifiedTimestamp": "1404619663", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Ability to create a \"mother/parent\" project for regional delivery type projects", | |
"Type": "Enhancement", | |
"details": [ | |
"\nIn cases such as regional delivery types of projects, DoE has requested the ability to create a 'mother/parent' project which allows proponents to report outcomes, issues and progress at a master project (head agreement) level.\r\n\r\nA short-term work around for this would be to create a project shell within the existing design framework in which the only activities are reporting activities and which has links to each of the sub-projects in the 'project stories' section of the overview page. \r\n\r\nIdeally something more robust and specifically designed is probably desirable, but would need to consider implications around re-use of information in sub-projects for process stream-lining, dashboard and numeric data/metrics impacts, activity relationships and the consistency of schedules and aggregated data (eg. parent and sub-project costs, targets, etc.), the flow-on implications of add activities and data to both the parent and sub-projects, etc.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "738", | |
"Modified": "Jul 06, 2014 04:30:40", | |
"ModifiedTimestamp": "1404621040", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Ability to colour-code sites/dots on maps by selected attribute facets", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE requirement\r\n\r\nThis request is for simple facet-based colouring of sites/dots on the fieldcapture home page map, similar to that provided on the ALA BIE records map. \r\n\r\nA specific case requested would be for differentiation between programmes displayed on the map, but there are also other attributes where colour differentiation would significantly add value to the mapped view. These are to be provided following further analysis.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "748", | |
"Modified": "Jul 07, 2014 02:17:11", | |
"ModifiedTimestamp": "1404699431", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Ability to insert a javascript widget (youtube, vimeo, etc) link to display and play embedded videos on the Overview page", | |
"Type": "Enhancement", | |
"details": [ | |
"\nDoE want to have more effective ways for people to be able to tell stories about the outcomes of their projects. One important mechanism for doing this is with videos and they want the ability to attach both links to external video sources as well as to embed playable clips within the project overview page and also within a \"Stories\" tab on the home page of MERIT.\r\n\r\nThis should be added via the project ADMIN tab and should display on the project Overview tab within the column of published images on the LHS of the page.\r\n\r\nDesign of the \"Stories\" tab for the MERIT home page is still to be developed.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "377", | |
"Modified": "Jul 06, 2014 03:42:01", | |
"ModifiedTimestamp": "1404618121", | |
"Owner": "chris.godwin.ala", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Stage numbering not behaving as expected", | |
"Type": "Defect", | |
"details": [ | |
"\nSub-programme allocations within a programme can be commenced at any time of the year and hence stage numbering (starting at stage 1 and allowing mid-year and/or full year reporting milestones) should be aligned with the commencement of the sub-programme, not fixed dates governed by the commencement of the higher level programme.\r\n\r\nThe first set of activities in chronology up to the next closest milestone date (ie. either Dec 31 OR Jun 30) should be designated as stage 1.\r\n\r\nDev is currently indicating activities created in a new project and starting in Nov '13 as the project starting in stage 2 - see: \r\n ", | |
"\r\n\r\nI thought after creating some activities that it might be based on the planned project start date, which for this project was Apr '13. This would put created activities into the 2nd project period and would be understandable, despite looking a bit strange without the project planned start date context. However, on changing the project planned start date to Sep '13 and refreshing the activity table, there was no change to the stage settings - I expected them to update to show the 1st set of activities in stage 1, 2nd in stage 2, etc.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "322", | |
"Modified": "Dec 10, 2013 12:47:29", | |
"ModifiedTimestamp": "1386679649", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "fieldCapture - Project manager select and update project", | |
"Type": "Defect", | |
"details": [ | |
"\nNavigating to the project details section is easy. The section is generally fine. Not too much excess information. It would be significantly easier (given five year length of projects)if date selections could be moved by years, not just months. \r\n\r\nThe Plans & Reports section. The interface is pretty reasonable if you don't have an internal system (given the level of detail being entered). To create whole MERI Plan in this format, would be quite time consuming. If this portion was mandated it would not be unreasonable (as it is only required annually/as needed - entered once at start of project and updated annually or as required). \r\n\r\nThere appear to be key sections of the MERI Plan missing from the current layout (KEQ, outputs, KPI, risk). \r\n\r\nAdding sites. Again this is ok, if you don't have another system. I couldn't identify any particular issues. However we are collecting significantly more detailed information about the actual works (e.g. fenclines, etc) and linking this to our financial information through a 'job code', using the DEPI outputs. \r\n\r\nAdditionally there is no link in the MERIT tool between the 'site' extent and the outputs (in a spatial sense). I could enter a site extent of trillions of hectares on a 0.5ha site polygon. The DEPI outputs enforce the relationship of the spatial object with the reportable amount (or require a count of spatial features, where events are held and additional information, such as number of particpants).\r\n\r\nDouble entry of this data (especially with the generalisations required to meet the current approach) would be wasteful and redundant. It would be very useful to a Landcare Group or similar sized/organised entity. However, as an organisation with existing systems, we would much prefer to have a mandated template (e.g. Excel) which we can produce from our systems and upload. \n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "495", | |
"Modified": "Jul 17, 2014 05:45:45", | |
"ModifiedTimestamp": "1405575945", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Output tracking view in MERIT", | |
"Type": "Enhancement", | |
"details": [ | |
"\nGrant Managers currently have independent locally developed tracking sheets (excel and access) which they use to track implementation against outputs. A relatively minor change to the system would facilitate the creation of a view of the MERIT data that would save significant time and effort for Grant Managers and would eliminate the need for them to operate shadow systems. It would also be of value to grantees in tracking the implementation of outputs against contracted outputs on a stage-by-stage basis.\r\n\r\nThis would require planned (target) outputs to be set on an activity-by-activity basis rather than at the whole project level as is currently that case. Changing this would require consultation with stakeholders.\r\n\r\nThe new view would then be a matrix of activities (with target outputs) on the Y-axis vs. a stage-based timeline on the X-axis, showing the target and implemented values within each stage - eg. using progress bars similar to those in the project dashboard. An aggregated stage-based summary by activity type may also be relevant where there is more than one activity of the same type within a stage.\r\n\r\n\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "496", | |
"Modified": "Jul 17, 2014 02:15:44", | |
"ModifiedTimestamp": "1405563344", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Program level dashboard", | |
"Type": "Enhancement", | |
"details": [ | |
"\nPart of the original MERIT requirement spec was for a program level dashboard to provide aggregated summaries of data from projects. these need to be framed in a manner which reflects generalised program needs, probably best based on a aggregated set of program KPIs from all current programs and anticipating what might be wanted in future programs, based on data being collected in current activity and assessment forms.\r\n\r\nThere is still a lot of analysis work to be done to work out what is needed and how to use the data being collected to produce the required views.\r\n\r\nThe first version of this dashboard is likely to be required by late February 2014 around the closure of the current reporting period.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "739", | |
"Modified": "Jul 06, 2014 04:39:52", | |
"ModifiedTimestamp": "1404621592", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Management Practice Change output: aggregate select list classes into reporting classes", | |
"Type": "Enhancement", | |
"details": [ | |
"\nNeed to aggregate some select list classes for industryType to enable reporting at an aggregate level for horticulture and broadacre cropping. \r\n\r\nThis will involve adding aggregation JSON to the 'Management Practice Change Details' output data model.\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "740", | |
"Modified": "Jul 06, 2014 04:47:37", | |
"ModifiedTimestamp": "1404622057", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Retain activity header data entered after moving focus into output sections", | |
"Type": "Defect", | |
"details": [ | |
"\nMERIT user notified issue:\r\n\r\nWhenever we edit some information in an Activity, it makes us re-enter the 'Actual Start' and 'Actual Finish' dates for that Activity before it will save the new information we have entered. Why aren't the Actual Start and Finish dates we've previously entered not retained like all other information we have entered?\r\n\r\nNeed to test!\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "741", | |
"Modified": "Jul 06, 2014 04:50:24", | |
"ModifiedTimestamp": "1404622224", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Unexpected error message when deleting an activity", | |
"Type": "Defect", | |
"details": [ | |
"\nIssue reported by user:\r\n\r\nError message displays when deleting activity: 'Failed to delete activity: error 500'. Refreshing page reveals the deletion does work, but it throws an error message. E.g. RGD14-012E-4 and LSP-991913-1432\r\n\r\nNeed to test!\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "743", | |
"Modified": "Jul 06, 2014 05:01:40", | |
"ModifiedTimestamp": "1404622900", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "print function does not copy across populated fields after entering data", | |
"Type": "Defect", | |
"details": [ | |
"\nUser submitted issue (via DoE):\r\n\r\nThe print function does not copy across populated fields after entering data to the field or once the Activity progress status is \u2018finished\u2019.\r\n\r\nNeed to test!\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Defect", | |
"ID": "746", | |
"Modified": "Jul 06, 2014 05:12:04", | |
"ModifiedTimestamp": "1404623524", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Grant manager not receiving stage report notification email", | |
"Type": "Defect", | |
"details": [ | |
"\nUser submitted issue (via DoE #127):\r\n\r\nGrant managers did not receive an email notifying that report for project Grant Id: X0000004479G had been submitted. \r\n\r\nNeed to test!\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "485", | |
"Modified": "Dec 19, 2013 00:33:47", | |
"ModifiedTimestamp": "1387413227", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Complete and test assessment form - Vegetation Assessment - BioMetric (NSW)", | |
"Type": "Enhancement", | |
"details": [ | |
"\nComplete and test assessment form - Vegetation Assessment - BioMetric (NSW)\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "FieldCapture, Priority-Medium, Type-Enhancement", | |
"ID": "487", | |
"Modified": "Dec 19, 2013 00:31:51", | |
"ModifiedTimestamp": "1387413111", | |
"Owner": "CoolDad67", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Complete and test assessment form - Vegetation Assessment - NVCA&M (WA)", | |
"Type": "Enhancement", | |
"details": [ | |
"\nComplete and test assessment form - Vegetation Assessment - NVCA&M (WA)\n" | |
], | |
"project": "FieldCapture" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "207", | |
"Modified": "Oct 18, 2013 04:15:40", | |
"ModifiedTimestamp": "1382069740", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Navigation - for validators - Pre Christmas", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Nov 22, 2011 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 22, 2011 \r\nProject admin page should be added to the breadcrumb for all admin pages as second item\r\n Nov 22, 2011 Project Member #1 [email protected] \r\n Issue 25 has been merged into this issue.\r\n Nov 22, 2011 Project Member #2 [email protected] \r\n(No comment was entered for this change.)\r\n Summary: Navigation - for validators - Pre Christmas Nov 22, 2011 Project Member #3 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: Type-Enhancement Priority-High Aug 7, 2012 Project Member #4 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: -Priority-High Priority-Medium\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "208", | |
"Modified": "Oct 18, 2013 04:18:30", | |
"ModifiedTimestamp": "1382069910", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Georeferencing tool standalone - Post Christmas unless resource becomes available", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Nov 22, 2011 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 22, 2011 \r\nSingle page for access in VP that is standalone \r\n Nov 22, 2011 Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: Type-Enhancement Priority-Medium Jan 11, 2012 Project Member #2 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: Milestone-2012Q1 Aug 7, 2012 Project Member #3 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: -Milestone-2012Q1 Milestone-Unsure\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "691", | |
"Modified": "Jun 12, 2014 23:22:07", | |
"ModifiedTimestamp": "1402615327", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "New single section template", | |
"Type": "Enhancement", | |
"details": [ | |
"\nCreate a new template that does not break fields into categories, but rather simply lays out fields in two (optionally configurable?) columns. Image should consume full width at the top of the screen.\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "694", | |
"Modified": "Jun 13, 2014 00:01:56", | |
"ModifiedTimestamp": "1402617716", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Spreadsheet template", | |
"Type": "Enhancement", | |
"details": [ | |
"\nCreate a new template that will collect fields in the 'dataset' category as columns in a spreadsheet.\r\n\r\nConsider using slickgrid.js\r\n\r\nOne approach would be to build a set of hidden form fields just before submit, from the rows and columns in the spreadsheet.\r\n\r\nThings to consider:\r\n\r\n* Revisiting page needs to rebuild the spreadsheet from existing fields\r\n* Navigating the spreadsheet should be easy and intuitive (arrows, enter key, tab and backspace, for example)\r\n* Support for validation rules\r\n* Some field types might benefit from custom rendered cells (dropdowns, autocomplete, dates)\r\n\r\n\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Defect", | |
"ID": "695", | |
"Modified": "Jun 13, 2014 00:12:58", | |
"ModifiedTimestamp": "1402618378", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Implement/improve Achievement/badges in BVP", | |
"Type": "Defect", | |
"details": [ | |
"\nPossible approach is as follows:\r\n\r\nCreate a full text index of task and fields (stand alone SOLR instance)\r\n * Need ability to reindex everything on demand (if we decide to index more)\r\n * Need to reindex fields and tasks as they are saved or validated\r\n * This index will also be useful for calculating various stats, so some thought needs to go into how to index them\r\n\r\nUse SOLR faceting queries to determine if particular thresholds/achievements have been reached\r\n * Achievements, with their rules and badges, will be stored in the database\r\n * New achievements can be added on the fly through an admin page\r\n * A 'UserAchievement' records if a user has earned an achievement, along with the date it was earned\r\n * After each submission/validation the list of unearned achievements is processed (asynchronously - Quartz?), and each SOLR query is executed to determine eligibility. If new achievements are earned, a flag could be set on the user object indicating that during the next page refresh some sort of notification should be made visible indicating new achievements (link to dashboard)\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "696", | |
"Modified": "Jun 13, 2014 00:26:18", | |
"ModifiedTimestamp": "1402619178", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Fine grained (Institution level) permissions for BVP", | |
"Type": "Enhancement", | |
"details": [ | |
"\nWith the creation of the Institution domain object, we should provide a new tier of permissions that allow institutions greater autonomy over managing their expeditions, whilst protecting other expeditions from accidental modification/deletion.\r\n\r\nNew (BVP application managed) roles 'Institution_Admin' and 'Institution_Validator' need to be created, which are always linked with an institution id. It is conceivable that some users will have multiple Institution_Admin and Institution_Validator roles, each with a different institution id.\r\n\r\nInstitution_Admins can:\r\n* Create new expeditions that are implicitly linked to the institution. If a user has more than one \"Institution_Admin\" role, a list of institutions should be provided. Perhaps always show a drop down of institutions - with either one or many institutions?\r\n* Assign institution_admin role for their institution to other users (again the list of institutions is constrained by their own roles)\r\n* Assign \"Institution_Validator\" roles to users\r\n* Modify institution profile details (description, logos, contact details etc)\r\n* Manage institution picklist items (collection codes?)\r\n* Manage institution templates. All templates will be readonly by default, but can be cloned and attached to an institution. \r\n\r\nConsider putting all permission checks in a service so that the rules can be easily codified:\r\n* BVP_ADMIN can do anything\r\n* Institution_Admin can do anything to institution expeditions\r\n* Institution_Validator can validate any expedition of that institution\r\n* Existing project_validator roles still need to be honoured\r\n* BVP_USER can transcribe only\r\n\r\n \n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "752", | |
"Modified": "Jul 10, 2014 06:14:09", | |
"ModifiedTimestamp": "1404972849", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Add tutorial links and picklist settings to create project wizard", | |
"Type": "Enhancement", | |
"details": [ | |
"\nThere probably should be steps in the create new expedition wizard for tutorial links and selecting a Collection picklist code.\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Defect", | |
"ID": "753", | |
"Modified": "Jul 10, 2014 06:15:47", | |
"ModifiedTimestamp": "1404972947", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Help text in preview template shows escaped HTML ", | |
"Type": "Defect", | |
"details": [ | |
"\nHelp text bubbles in the template preview are displaying html tags instead of rendering them. \r\n\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BHL, Priority-Medium, Type-Enhancement", | |
"ID": "206", | |
"Modified": "Aug 09, 2013 00:25:14", | |
"ModifiedTimestamp": "1376007914", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Update BHL search index", | |
"Type": "Enhancement", | |
"details": [ | |
"\nJust logging this issue. We are already making progress...\n" | |
], | |
"project": "BHL" | |
}, | |
{ | |
"AllLabels": "ImageService, Priority-Medium, Type-Defect", | |
"ID": "729", | |
"Modified": "Jul 03, 2014 01:29:56", | |
"ModifiedTimestamp": "1404350996", | |
"Owner": "david.baird.ala", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Old skool breadcrumbs", | |
"Type": "Defect", | |
"details": [ | |
"\nThe image service pages are using the old style breadcrumbs:\r\n\r\nOld skool:\r\n\r\n", | |
"\r\n\r\nnew skool:\r\n\r\n", | |
"\r\n\n" | |
], | |
"project": "ImageService" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, Spatial-Portal, SpatialPortal, Type-Task", | |
"ID": "73", | |
"Modified": "Aug 08, 2013 23:28:40", | |
"ModifiedTimestamp": "1376004520", | |
"Owner": "drdavematthews", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Test restore Prod - Test", | |
"Type": "Task", | |
"details": [ | |
"\nOriginal Issue - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Jun 16, 2011 \r\nBackups are occurring but for peace of mind, it would be good to do a test restore of the production system to the test vm. There is currently nothing happening on test that will be affected.\r\n\r\nDave: Can this be organized??\r\n Aug 9, 2011 #1 [email protected] \r\n(No comment was entered for this change.)\r\n Status: Started Oct 6, 2011 Project Member #2 [email protected] \r\nreset non-biocache issues to High\r\n Labels: -Priority-Critical Priority-High May 6, 2012 Project Member #3 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: -Priority-High Priority-Low Jul 11, 2013 Project Member #4 [email protected] \r\nIs this still an issue? I suspect so.\r\n Summary: Test restore Prod - Test (was: Test restore Prod to Test) Cc: -ajay.ranipeta [email protected] moyesyside [email protected] Labels: -Priority-Low Priority-Medium\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, SpatialPortal, Type-Defect", | |
"ID": "264", | |
"Modified": "Sep 16, 2013 04:23:34", | |
"ModifiedTimestamp": "1379305414", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "SP searching on genus only gives a no-show for some species", | |
"Type": "Defect", | |
"details": [ | |
"\nSpatial Portal. Adding a species to the map works for the genus 'Eucalyptus' but not 'Eremophila'\r\n\r\nExample\r\nSpatial Portal\r\nAdd to Map | Add species | Search for species by scientific or common name\r\nEnter the genus name: Eremophila\r\nDrop-down list shows about 40 common names, no scientific names of species (yet) and not the genus name (NOT GOOD).\r\n\r\nExpect to see\r\nA drop-down list that includes the genus name. In the example above Eremophila\r\n\r\nAnother example where no genus is shown (I didn't find many though I searched using about 20 other generic names)\r\nGoodenia\r\n\r\n(Is this only a problem where there are many common names that include the genus name?)\r\n\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "281", | |
"Modified": "Nov 08, 2013 05:39:38", | |
"ModifiedTimestamp": "1383889178", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "BioCache faceting fails when choosing refine with multiple values", | |
"Type": "Defect", | |
"details": [ | |
"\nIn BioCache, the dialog box that opens when wanting to refine a facet gets stuck, sometimes. Sometimes with an empty dialog box, sometimes with a full dialog box, sometimes with a partially filled dialog box. It depends on the browser.\r\n\r\nIn BioCache\r\nExample using Chrome25 for \"Frogs\" ", | |
"\r\nFacet on Scientific name, Country, or Specimen type, - spinning wheel\r\nFacet on Common name, or IBRA, or Collector - no problems\r\n\r\nThis is a browser-dependent problem:\r\nGoogle Chrome - spinning wheel - see diagram\r\nFF25 - not apparent in FF25\r\nIE9 - pop-up box incomplete - see diagram\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "282", | |
"Modified": "Nov 08, 2013 05:38:31", | |
"ModifiedTimestamp": "1383889111", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "lifeform facet filter fails", | |
"Type": "Defect", | |
"details": [ | |
"\nIn BioCache, using Lifeform filter with other filters fails.\r\nSometimes...\r\n\r\nThree examples: The first two fail, the third example is OK\r\nExample 1 (fail)\r\nquick search = everything\r\nFilter on Australia + Birds (Problem - results leave Australia out)\r\n", | |
"\r\n\r\nExample 2 (Fail)\r\nquick search = animals\r\nFilter on Australia + Birds (Problem - results leave Australia out)\r\n", | |
"\r\n\r\nExample 3 (success)\r\nquick search = birds\r\nFilter on Australia + Birds (NOT a Problem - Australia is included)\r\n", | |
"\r\n\r\nOperating system: Win7\r\nBrowser: FF25, Chrome30, IE9\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Alerts, Priority-Medium, Type-Enhancement", | |
"ID": "284", | |
"Modified": "Nov 08, 2013 05:58:56", | |
"ModifiedTimestamp": "1383890336", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Alerts for new records for species - a link would help", | |
"Type": "Enhancement", | |
"details": [ | |
"\nWANTED: When a user is alerted of a new record for a species, can we have a link to a list of the ***RELEVANT*** changes in their alert email \r\n\r\nCurrently, when a user is notified with an alert for a nominated species, their email gives a link for ***ALL*** records that have been changed.\r\n\r\nie what is missing in the current link is the faceting/filtering that is relevant to their species of interest.\r\n\n" | |
], | |
"project": "Alerts" | |
}, | |
{ | |
"AllLabels": "BIE, Priority-Medium, Type-Defect", | |
"ID": "560", | |
"Modified": "Feb 05, 2014 21:30:21", | |
"ModifiedTimestamp": "1391635821", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "BIE search fails if I include brackets", | |
"Type": "Defect", | |
"details": [ | |
"\nA search for Kookaburra fails in BIE. It appears to be a sub-genus problem.\r\n\r\nSearch term\r\nDacelo (Dacelo) novaeguineae ***FAILS*** \r\n", | |
"\r\nError message: \r\nSearch for Dacelo (Dacelo) novaeguineae did not match any documents\r\n\r\nThe following search terms work:\r\nKookaburra\r\nDacelo novaeguineae\r\nDacelo () novaeguineae\r\n\r\nThe same failure occurs with other species which have sub-genus in brackets - eg bees:\r\nHylaeus (Prosopisteron) baudinensis\r\nHomalictus (Homalictus) urbanus\r\n\r\nI occasionally got an error message like this:\r\nError\r\nFailed calling web service. class java.io.IOException Server returned HTTP response code: 500 for URL: ", | |
" URL= ", | |
".\r\nURL: ", | |
"\r\n\r\n\n" | |
], | |
"project": "BIE" | |
}, | |
{ | |
"AllLabels": "Priority-Medium, SpatialPortal, Type-Enhancement", | |
"ID": "703", | |
"Modified": "Jun 16, 2014 05:21:05", | |
"ModifiedTimestamp": "1402896065", | |
"Owner": "leebelbin", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Implied absence data in at least one dataset raises procedural issue", | |
"Type": "Enhancement", | |
"details": [ | |
"\nA placeholder for now:\r\n\r\nI had a discussion with Mike Austin (CSIRO) about a dataset quite a few of us have worked on (Mike, Margaret Cawsey, Nick Nicholls etc) and it transpires at least one version of this dataset has come into the ALA via NSW Parks or subsequent equivalent.\r\n\r\nThe dataset contains the presence of TREE species in .25 or .1ha sites. The implication is that we can infer many absences of tree species on all of these ~10,000 sites. This would imply we could have of the order of ~>100,000 absence records.\r\n\r\nIt should be possible to automate or at least semi-automate the generation of these absence records at the survey sites using known tree distributions (via a geographic or environmental convex hull or equivalent)? \r\n\r\nThis issue has also exposed another GAP in the ALA: The inability to generate sites x species matrices from survey points. This was what Mike Austin was asking about at the ALA Symposium. If we eventually get AEKOS data or any other bio-survey data, this will be a BASIC requirement. This is a separate but related issue that I'll raise.\n" | |
], | |
"project": "SpatialPortal" | |
}, | |
{ | |
"AllLabels": "BIE, Priority-Medium, Type-Defect", | |
"ID": "164", | |
"Modified": "Aug 14, 2013 02:49:45", | |
"ModifiedTimestamp": "1376448585", | |
"Owner": "leebelbin", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Regions - Add Australia", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Mar 27, 2012 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Mar 27, 2012 \r\nThere are all sorts of ways for chopping up the nation, states, LGAs, IBRA and IMCRA regions CMAs and so forth.\r\nCan we have a region for Australia.\r\n\r\nI know this is a sensitive problem (Ask Lee: \"Where is Australia?), but maybe it might be good to have a section for Australia\r\nFor example:\r\nContinental Australia\r\nAustralia including Antarctica\r\nAustralia with EEZ\r\n... and so on.\r\n\r\n Mar 27, 2012 Project Member #1 [email protected] \r\ncc-ing Lee on this as he's been looking into the uber Australia layer.\r\n\r\ni think the request makes sense.\r\n Cc: [email protected] Mar 27, 2012 Project Member #2 [email protected] \r\nCase was put to Geoscience Australia 2 months ago. They have agreed that we are not the only agency needing an Australian Region definition. Emailed about 2 weeks ago, and it is progressing. I have to wonder why GA didn't have such a layer on tap.\r\n\r\nAll said, these data will be dynamic. International positioning continues in relation to remote territories.\r\n Mar 27, 2012 Project Member #3 [email protected] \r\nI think there could be a lot of Australias, or at least a lot of views of Australia. Your choice of view of Australia will depend on what you want to present. \r\n\r\nCurrently, the Regions part of ALA very quickly presents summary information for a pre-defined space. eg Falcons in New South Wales, fish species in Riverina. However a state is the biggest region so far available. \"Regions\" is currently not set up to deliver anything for the nation, or the continent, or even the sum of the states and territories.\r\n May 6, 2012 Project Member #4 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: Priority-Low Mar 13, 2013 Project Member #5 [email protected] \r\nJust noting this has been on the issue tracker for a year with no resolution. I doubt we'll ever get something from GA. Can we define this ourselves ?\r\n Mar 13, 2013 Project Member #6 [email protected] \r\nGood idea. \r\n Mar 14, 2013 Project Member #7 [email protected] \r\nJust emailed Mark Alcock if the prposed GA web services for coastal/maritime boundaries have been implemented. Fingers crossed.\n" | |
], | |
"project": "BIE" | |
}, | |
{ | |
"AllLabels": "Browser-IE, Priority-Medium, SpatialPortal, Type-Defect", | |
"ID": "520", | |
"Modified": "Jan 15, 2014 02:32:16", | |
"ModifiedTimestamp": "1389753136", | |
"Owner": "linda.riq", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Extra scroll bars in tool wizard", | |
"Type": "Defect" | |
}, | |
{ | |
"AllLabels": "BIE, Brokenlinks, Priority-Medium, Type-Defect", | |
"ID": "530", | |
"Modified": "Jan 17, 2014 01:32:49", | |
"ModifiedTimestamp": "1389922369", | |
"Owner": "linda.riq", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Broken links in Iconic Species pages", | |
"Type": "Defect" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "192", | |
"Modified": "Aug 13, 2013 07:06:11", | |
"ModifiedTimestamp": "1376377571", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Suggestion for new feature: Where is my data set?", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Jun 12, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], Jun 12, 2012 \r\nThis enhancement refers to MY PROFILE and DATASETS\r\n\r\nOverview of feature/enhancement:\r\nCurrently when people submit a dataset to ALA (", | |
"), they push the SUBMIT button, and then ... nothing. If a week passes, where is their data? Checking every few days is a tedious and unrewarding chore.\r\n\r\nUser story describing steps to use functionality:\r\nProbably on the MY PROFILE page (", | |
")\r\nAdd a feature that shows VIEW MY DATASETS\r\n\r\nWhat the feature should look like (example URLs accepted):\r\nMY DATASETS\r\nProbably be a subset of ATLAS DATA SETS (", | |
")\r\nThis page should also include those datasets that have been submitted but not yet have a formal dataset page created.\r\n\r\nCan a dataset page be created at submit time?\r\nIf so, the dataset page could get its metadata from the details filled in at data upload time.\r\n\r\nTo keep the user informed, each step of the upload process could be shown as a timestamp at the bottom of the dataset page with an estimate of next step.\r\n\r\nExample\r\nInitial submission: 2012-06-13 13:16:45.0\r\nData quality tests: 2012-06-14 10:00:00.0\r\nData upload: expected 2012-06-21 12:00:00.0\r\nlast updated: 2012-06-14 10:00:00.0\r\n\r\n Today (93 minutes ago) Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Owner: [email protected]\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "BVP, Priority-Medium, Type-Enhancement", | |
"ID": "209", | |
"Modified": "Aug 09, 2013 04:44:22", | |
"ModifiedTimestamp": "1376023462", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Archiving existing completed projects - Post Christmas", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Nov 22, 2011 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 22, 2011 \r\nNed to develop a strategy for archiving completed project- do we still make them available for viewing or do we take them off the front page\r\n Nov 22, 2011 Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: Type-Enhancement Priority-Medium Jan 11, 2012 Project Member #2 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: Milestone-2012Q1 Jan 19, 2012 Project Member #3 [email protected] \r\nThis should be looked after by the new front page and expeditions page.\n" | |
], | |
"project": "BVP" | |
}, | |
{ | |
"AllLabels": "BIE, Priority-Medium, Type-Defect", | |
"ID": "165", | |
"Modified": "Aug 13, 2013 06:35:38", | |
"ModifiedTimestamp": "1376375738", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Regions - Explore-by-date resets selected species", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Mar 27, 2012 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Mar 27, 2012 \r\nThe explore-by-date slider bars is a good tool. But when using it the selected species is lost.\r\n\r\n", | |
"\n1. Home/ Locations / regions / New South Wales\r\n", | |
"\r\n2. Birds / species = Falco \r\n3. Choose Black falcon | Falco (Hierofalco) subniger (sorry, you need to scroll through 7 pages to get there, but this is important)\r\n4. Run the time-lapse.\r\n\r\nWhat is the expected output? \r\nA time-lapse of the black Falcon\r\n\r\nWhat do you see instead?\r\nA time lapse of all birds\r\nAnd ... I have lost the selection for Black Falcon. (7 pages away.)\r\n\r\nContinuing...\r\n5. Choose Black Falcon | Falco (Hierofalco) subniger (again)\r\nNote that sliders are where they finished after time lapse. Number of records is for the last decade.\r\n\r\n6. Alter one slider\r\nAgain ... I have lost the selection for Black Falcon.\r\n\r\n", | |
"\n\r\n Mar 27, 2012 Project Member #1 [email protected] \r\ncc-ing Mark for thoughts.\r\n Owner: [email protected]\n" | |
], | |
"project": "BIE" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "179", | |
"Modified": "Aug 09, 2013 00:08:57", | |
"ModifiedTimestamp": "1376006937", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Post R5 - Collectory - type specimens", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Nov 2, 2010 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 2, 2010 \r\nConsider adding breakdown of type specimines within a collection on the records tab of the collection. -originally entered by Benay.\r\n\r\n Nov 2, 2010 Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: -Type-Defect Type-Enhancement\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "180", | |
"Modified": "Aug 09, 2013 00:09:09", | |
"ModifiedTimestamp": "1376006949", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Review data model for institution hierarchies", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Nov 23, 2010 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Nov 23, 2010 \r\nWe currently model collections as belonging to a single institution. Hierarchies are achieved by institutions having child institutions.\r\nOccurrence records map to a single institution.\r\nThis makes aggregation of record stats difficult for parent institutions.\r\n\r\nReview and see if we can adopt a better model.\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "182", | |
"Modified": "Aug 09, 2013 00:09:29", | |
"ModifiedTimestamp": "1376006969", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Split address into postal and physical", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Dec 2, 2010 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Dec 2, 2010 \r\nPost box and street are currently conflated and cannot be extracted for either use. Assumes same city and postcode for both.\r\n\r\nNeed clear separation of the 2 addresses.\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "185", | |
"Modified": "Aug 09, 2013 00:10:16", | |
"ModifiedTimestamp": "1376007016", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Scientific names for collection should include rank.", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Apr 10, 2011 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Apr 10, 2011 \r\nNames without rank are hard to re-use, eg for eml or automation of processing.\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "186", | |
"Modified": "Aug 09, 2013 00:10:28", | |
"ModifiedTimestamp": "1376007028", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Add curatorialUnit to collections metadata", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Apr 11, 2011 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Apr 11, 2011 \r\nWe currently infer units (as in specimens, cultures, samples) from the collection type and use the unit in displaying numbers, eg 32,000 specimens.\r\n\r\ntdwg ontology has a jgtiCuratorialUnit field. We should adopt the unqualified name and explicitly record the desired units for a collection.\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "187", | |
"Modified": "Aug 09, 2013 00:10:41", | |
"ModifiedTimestamp": "1376007041", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Support self-registration for citizen science portals", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Jul 10, 2011 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Jul 10, 2011 \r\nAsk for the BDRS base url. Read metadata file from the instance and create a data resource entry.\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Collectory, Priority-Medium, Type-Enhancement", | |
"ID": "189", | |
"Modified": "Aug 09, 2013 00:11:04", | |
"ModifiedTimestamp": "1376007064", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Accepted", | |
"Summary": "Add archive download link to data resource pages", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Jan 29, 2012 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Jan 29, 2012 \r\nAdd link of the form: biocache.ala.org.au/archives/<UID>/<UID>_ror_dwca.zip\r\n\r\neg ", | |
"\r\n\r\nShow popup to ask for download reason.\r\n\r\nLog download event. Use new 'archive download' identifier.\n" | |
], | |
"project": "Collectory" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "659", | |
"Modified": "May 30, 2014 05:46:18", | |
"ModifiedTimestamp": "1401428778", | |
"Owner": "[email protected]", | |
"Priority": "Medium", | |
"Status": "Started", | |
"Summary": "Occurrence records with invalid layer sampling?", | |
"Type": "Defect", | |
"details": [ | |
"\nSummaries of occurrence queries from Kristen Williams are suggesting (serious?) anomalies in the sampling of spatial layers of some records during processing. For example, if a query is constructed on \r\n\r\nCountry = n/a AND\r\nIBRA = n/a AND\r\nIMCRA = n/a AND\r\nel884 (bathymetry and elevation) = n/a\r\n\r\nit should only return records that occur outside Australia. The following query however\r\n\r\n", | |
" \r\n\r\nproduces 40,954 records, most of which ARE in 'Australia' and are terrestrial. \r\n\r\nA few records are marine (correctly or not as I haven't checked yet) but should still be on the bathy/topo layer (and IMCRA). \r\n\r\nThere are also a few on offshore islands, which should also be on the bathy/topo layer, if not IMBRA or IMCRA - and they should also be 'Australia' but that may be another issue. \r\n\r\nThe WKT (bounding box) here just includes Australia and associated islands. \r\n\r\nPS: Diagnosis of classification of the records would be made easier if #658 were solved.\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "98", | |
"Modified": "Aug 09, 2013 05:28:50", | |
"ModifiedTimestamp": "1376026130", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Fish or Fishes", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Today (16 hours ago) - ", | |
"\r\n\r\n\r\nReported by [email protected], Today (16 hours ago) \r\nI have been told that when we refer to 'fish' as a lifeform we should use the word 'fishes'\r\nSee ", | |
"\r\n\r\nThe word 'fish' should be changed to 'fishes' when referring to a lifeform.\r\n\r\n", | |
"\nAn example:\r\nAustralian Museum Ichthyology collection. in the graph of records by higher level group: \r\nAxis is Arthropods Fish Insects Reptiles\r\n\r\n", | |
"\nAxis is Arthropods ***Fishes*** Insects Reptiles \r\n\r\nWhat version of the product are you using? On what operating system?\r\n2013\r\n\r\nPlease provide any additional information below.\r\nThe term 'fish' is probably incorrectly used in a bunch of places.\r\n\r\nThis is a low priority fix.\r\n fish or fishes.png 4.7 KB \u00a0 View \u00a0 Download\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Enhancement", | |
"ID": "112", | |
"Modified": "Aug 08, 2013 23:34:11", | |
"ModifiedTimestamp": "1376004851", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Support for SOLR 4.4", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Aug 4 (3 days ago) - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Aug 4 (3 days ago) \r\nAttached to this issue is the patch required to upgrade to SOLR4.4.0. This code base will not be committed into the trunk until we are ready to release biocache-service at SOLR 4.4 level.\r\n Aug 4 (3 days ago) Project Member #1 [email protected] \r\n(No comment was entered for this change.)\r\n Labels: SOLR Aug 5 (2 days ago) Project Member #2 [email protected] \r\nI didn't realise that there was a bug in one of my files. Here is that works\r\n SOLR4.4-integration.patch 31.1 KB \u00a0 View \u00a0 Download\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "113", | |
"Modified": "Aug 08, 2013 23:34:23", | |
"ModifiedTimestamp": "1376004863", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Quality tests failed to pick up Citizen Science record in wrong hemishpere", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Jul 9, 2013 - ", | |
"\r\n\r\n\r\nReported by [email protected], Jul 9, 2013 \r\nUser flagged an issue on 9 July 2013 \r\n", | |
"\r\n\r\nComment: Lat and Long are correct for this but Lat should be SOUTHERN hemisphere. i.e. -29.93... Does anyone check this stuff??\r\n\r\nNote that this is a fish, and so may be a cause for not checking for marine/non-marine \r\n\r\n", | |
"\n1. Citizen Science data is entered. Lat-long is given wrong hemisphere.\r\n(I know that Google Maps will show you where you are on the planet, but for some reason, this didn't work properly this time. The location given was too descriptive for Google Maps, so the marker would have had to be manually moved. Probably where the first error came in.)\r\n\r\n2. ALA Data quality tests do not detect any problems\r\nFailed quality tests: 0\r\nData warnings: 0\r\nPassed quality tests: 24\r\nMissing record properties: 11\r\nTest not ran (lack of data): 42 \r\n\r\nSome of the tests not run include\r\nLatitude is negated \tUnchecked (lack of data)\r\nCoordinates dont match supplied country \tUnchecked (lack of data)\r\n\r\nWhat is the expected output? \r\nA validity check that picks up wrong hemisphere, or out-of-country.\r\n\r\nWhat do you see instead?\r\nAll tests passed.\r\n\r\nWhat version of the product are you using? On what operating system?\r\nN/a\r\n\r\nPlease provide any additional information below.\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Enhancement", | |
"ID": "117", | |
"Modified": "Aug 19, 2013 03:03:04", | |
"ModifiedTimestamp": "1376881384", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "customisable field list for downloads", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Project Member Reported by [email protected], Oct 11, 2012 - ", | |
"\r\n\r\n\r\nProject Member Reported by [email protected], Oct 11, 2012 \r\nAdd a field picker to allow users downloading a data set to choose the fields included\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Enhancement", | |
"ID": "119", | |
"Modified": "Aug 13, 2013 07:10:40", | |
"ModifiedTimestamp": "1376377840", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Add MONTH to charts", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Jul 11, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], Jul 11, 2012 \r\nOverview of feature/enhancement:\r\nIn the CHARTS tab of the Occurrence Records page, add a bar chart for MONTH.\r\nie on this page: ", | |
"\r\n\r\nUser story describing steps to use functionality:\r\nA Bar chart for MONTH is really useful. It gives a clue to flowering time, or in the case of animals, when they are probably most likely to be active. It can really provide a good service.\r\n\r\nWhat the feature should look like (example URLs accepted):\r\n", | |
" \r\nSee the third chart.\r\n Jul 18, 2013 Project Member #1 [email protected] \r\ndone\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "121", | |
"Modified": "Aug 12, 2013 19:05:58", | |
"ModifiedTimestamp": "1376334358", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "A Flickr photo with more than one species", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Jun 15, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], Jun 15, 2012 \r\nFlickr photos tagged with more than one species are only being associated with a single species in ALA. They should be associated with each tagged species in the photo.\r\n\r\nFlickr-EOL photos can include tags for more than one species. EOL have defined rules for this, (see ", | |
" and see the FAQ: \"What if there is more than one species in the photo?\") - ie multiple tags are provided at only one taxonomic level.\r\n\r\n", | |
"\n1. Select a recent Flickr upload with say a BHL image. For example:\r\n", | |
"\r\nThis image has 8 butterflies. On Flickr it has multiple machine tags covering all the butterflies. (Some tags represent an old name.)\r\n2. This image is only linked to one species: Paralucia pyrodiscus\r\n\r\nWhat is the expected output? \r\nThat Flickr photo to be linked to all eight species that are tagged in the photo.\r\n\r\nWhat do you see instead?\r\nThe photo is only linked to one butterfly species on ALA.\r\n\r\nPlease provide any additional information below.\r\nImages that, for example, show species interactions will contain multiple taxa. ALA should be able to show that image\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Enhancement", | |
"ID": "122", | |
"Modified": "Aug 12, 2013 19:05:38", | |
"ModifiedTimestamp": "1376334338", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Biocache download checklist: more fields please", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], May 31, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], May 31, 2012 \r\nBeing able to download a checklist is great. Adding more fields, such as common name, lifeform, or other taxonomic levels would be very useful. \r\n\r\nOverview of feature/enhancement:\r\nI was wanting to get a list of the birds in Australia. Most bird people refer to birds by their common name.\r\n\r\nFor some of us, when we want to know the species in an area, we may only be familiar with common names. If a beast has no common name, and its scientific name appears in a list, what is it? A frog, a plant, or something else?\r\n\r\nIf ALA provides the species list as a spreadsheet, adding other known names will help.\r\n\r\n\r\nUser story describing steps to use functionality:\r\nWhen downloading a checklist, please provide\r\nGUID\r\nVernacular name\r\nLifeform\r\nKingdon\r\nPhylum\r\nClass\r\nOrder\r\nFamily\r\nGenus\r\nSpecies\r\nSubspecies\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Sandbox, Type-Defect", | |
"ID": "123", | |
"Modified": "Aug 12, 2013 19:17:48", | |
"ModifiedTimestamp": "1376335068", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Sandbox - missing vernacular name", | |
"Type": "Defect" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Enhancement", | |
"ID": "126", | |
"Modified": "Aug 12, 2013 19:30:59", | |
"ModifiedTimestamp": "1376335859", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Non-occurrence data", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], May 1, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], May 1, 2012 \r\nPeople have asked for access to associated data if it exists.\r\n\r\nOften a dataset is a set of results of measurements for a purpose, and a lot of extra information is recorded as well as the occurrence information which ALA shows. For example someone may be measuring leaf-thickness, or height of trees, or associated taxa.\r\n\r\nCurrently ALA does not show this extra info.\r\n\r\nIs there a way that this extra data can be discovered?\r\n\r\nDifficulties: This data probably won't come in any standard form - eg one person may measure eye-colour whereas the next person could measure iris-colour. However if we can pass this information on to a user, it would be a first step.\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "128", | |
"Modified": "Aug 08, 2013 23:38:03", | |
"ModifiedTimestamp": "1376005083", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Inconsistent pluralisation in the values of type_status", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Apr 16, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], Apr 16, 2012 \r\nAll the values of the type_status facet are singular except for paratypes.\r\n\r\n Screen shot 2012-04-17 at 8.38.16 AM.png 22.6 KB \u00a0 View \u00a0 Download\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Enhancement", | |
"ID": "130", | |
"Modified": "Aug 12, 2013 19:20:39", | |
"ModifiedTimestamp": "1376335239", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Faceting needs a re-think", | |
"Type": "Enhancement", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Mar 28, 2012 - ", | |
"\r\n\r\n\r\nReported by [email protected], Mar 28, 2012 \r\nOverview of feature/enhancement:\r\nOn the occurrence records page the FUNCTIONALITY of the faceting is very powerful.\r\nHowever its usability is tough.\r\n\r\nEarlier this week the ordering of the faceting changed. Before the change there were 'Form' and source-based faceting at the top - specimen type, collector, institution and so on. I was very familiar with the list and could quickly find important headings.\r\n\r\nAfter the change, there is now taxonomic information at the top, and although this might make good logical sense, the order has changed and I no longer know my way around the list. This is probably how a newbie finds it - a bit confusing, and what does it all mean?\r\n\r\nAny wonder with 41 categories, each with up to 3 options each. Over 100 lines, all with good information needing to be thought about and assessed: Do I need this facet? Or is there another one?\r\n\r\nSo, I think a re-think is necessary. How should this large amount of helpful information be better presented?\r\n\r\nA few ideas, if only to kick this along... \r\n1. Use colour to split between what (taxonomy), who (source, institution, collector), where (location), when (dates), how (images, DNA), other\r\n\r\n2. Present a core subset of filter categories to open with. These could be modified using the customise list.\r\n\r\n3. Present a set of 6 facet categories, each open as drop-down lists. A little like the selectable regions in the REGIONS page, with the ability to select more than one facet and category.\r\n\r\n4. The pie charts and bar charts work. Perhaps linking the charts to other facet categories? I'm not sure about this idea, as the charts are pretty clean now, and to sully them with more categories might make them unworkable. \r\n\r\n May 5, 2012 #1 [email protected] \r\nSome facets are now ordered alphabetically, rather than by popularity. Generally the order of each facet needs to be considered on its merits, eg collector, collection, scientific name, should be ordered by numbers of records; months and decades in chronological order; State conservation in an order that is consistent - say from least concern to extinct; and so on.\r\n\r\nI think it is worth thinking about how these facets are used when re-laying out their presentation.\n" | |
], | |
"project": "Biocache" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Sandbox, Type-Defect", | |
"ID": "136", | |
"Modified": "Aug 12, 2013 19:44:06", | |
"ModifiedTimestamp": "1376336646", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "sandbox - double-quotes not handled well", | |
"Type": "Defect" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Sandbox, Type-Enhancement", | |
"ID": "145", | |
"Modified": "Aug 09, 2013 05:31:46", | |
"ModifiedTimestamp": "1376026306", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Sandbox enhancements", | |
"Type": "Enhancement" | |
}, | |
{ | |
"AllLabels": "Biocache, Priority-Medium, Type-Defect", | |
"ID": "147", | |
"Modified": "Aug 08, 2013 23:43:42", | |
"ModifiedTimestamp": "1376005422", | |
"Owner": "moyesyside", | |
"Priority": "Medium", | |
"Status": "New", | |
"Summary": "Explore your area - inconsistent record count between facets & map points", | |
"Type": "Defect", | |
"details": [ | |
"\nOriginal Issue reported by Reported by [email protected], Jan 12, 2011 - ", | |
"\r\n\r\n\r\nReported by [email protected], Jan 12, 2011 \r\n", | |
"\n1. go to this url - ", | |
"\r\n2. left-click 'fungi' facet to limit results to fungi classification - note facet count in brackets is (280)\r\n3. now, 3 results will appear - the dark red result near the 'canberra international airport' has 160 occurrence records and the result near yarralumla has 359\r\n\r\nif you go to ", | |
" you will see that there are 500-odd fungi records which is consistent with the sum of the dots on the map\r\n\r\nmaybe the facet count is not rolling up counts from sub-groups?\r\n\r\nfirefox 3.6.11 on xp sp 3\n" | |
], | |
"project": "Biocache" | |
} | |
] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import sys | |
import csv | |
import json | |
import unicodedata | |
def create_json(file_name, column_names): | |
csv_file = open(file_name[0], 'r') | |
csv_reader = csv.DictReader(csv_file, column_names) | |
out = json.dumps( [row for row in csv_reader] ) | |
data = json.loads(out) | |
#print "number of issues found: %d" % len(data) | |
# simple report in HTML format into stdout | |
print '<html>' | |
print '<body>' | |
print '<table border="1">' | |
for issue in data: | |
text = unicodedata.normalize('NFKD', issue["AllLabels"]).encode('ascii', 'ignore') | |
labels = text.strip().split(",") | |
project = [] | |
for label_text in labels: | |
label = label_text.strip() | |
if len(label) == 0: | |
continue | |
if label.find("Type") > -1: | |
continue | |
if label.find("Priority") > -1: | |
continue | |
project.append(label) | |
# for issues that have 0 or multiple number of projects, print them out: | |
if len(project) != 1: | |
#print 'id: {}, project_label({}): {}'.format(issue["ID"], len(project), project) | |
if len(project) == 0: | |
err = "NO PROJECT" | |
if len(project) > 1: | |
err = "MULTIPLE ({}) PROJECTS".format(project); | |
print '<tr><td>{}</td><td>{}</td><td><a href="https://code.google.com/p/ala/issues/detail?id={}">{}</a></td></tr>'.format(issue["ID"], err, issue["ID"], issue["Summar\ | |
y"]) | |
print '</table>' | |
print '</body>' | |
print '</html>' | |
json_file = open(file_name[0] + ".json", 'w') | |
json_file.write(out); | |
if __name__=="__main__": | |
create_json(sys.argv[1:], ["ID","Type","Status","Priority","Owner","Summary","AllLabels","Modified","ModifiedTimestamp"]) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# some preliminary investigation in case google does not give us access to the deprecated/disabled issue API | |
# extracting issue IDs | |
curl https://code.google.com/p/ala/issues/list > ala_issues.out | |
grep 'id: ' ala_issues.out | |
grep 'id: ' ala_issues.out | sort | uniq | wc -l => 100 | |
# to clean the id string info from " id: 539}," to "539" (that is sort-able, etc.) | |
grep 'id: ' ala_issues.out | sed -e "s/^.*id: //g" -e "s/},*//g"|sort -h | |
# google page offers download in CSV | |
# single issue page/details is accessible like: | |
curl https://code.google.com/p/ala/issues/detail?id=77 >> issue-77.html | |
# looking at single issue-s details | |
ls | |
# ala_issues.out issue-511.html issue-77.html | |
grep "list?q=label:" issue-* | |
# issue-511.html: <a href="list?q=label:Type-Enhancement" | |
# issue-511.html: <a href="list?q=label:Priority-High" | |
# issue-511.html: <a href="list?q=label:SpatialPortal" | |
# issue-77.html: <a href="list?q=label:Priority-Medium" | |
# issue-77.html: <a href="list?q=label:Type-Enhancement" | |
# issue-77.html: <a href="list?q=label:Spatial-Portal" | |
# issue-77.html: <a href="list?q=label:SpatialPortal" | |
# join the 4 separate .csv file-s downloaded from https://code.google.com/p/ala/issues/list | |
cat ala-issues.csv ala-issues\ \(1\).csv ala-issues\ \(2\).csv ala-issues\ \(3\).csv >> ala-issues-all-2014-07-15.csv | |
# translate the .csv into json format (creates ala-issues-all-2014-07-15.csv.json | |
python csv2json.py ala-issues-all-2014-07-15.csv | |
# examine the output json file | |
cat ala-issues-all-2014-07-15.csv.json | python -m json.tool | |
# generates: | |
# - ala-issues-all-2014-07-15.csv.json for migration | |
# - and HTML table problem report is stored in ala-issues-all-2014-07-15.csv.html | |
# | |
python csv2json.py ala-issues-all-2014-07-15.csv > ala-issues-all-2014-07-15.csv.html | |
# get the name-s of all available projects | |
mbohun@firewolf:~/src/ala-misc.git/code.google-issues-2-github-issues> cat ala-issues-all-2014-07-17.csv.json | python -m json.tool | grep -e "\"project\"" | sort |uniq | |
"project": "Alerts" | |
"project": "ASBP" | |
"project": "AUTH" | |
"project": "AVH" | |
"project": "BHL" | |
"project": "BIE" | |
"project": "biocache" | |
"project": "Biocache" | |
"project": "Browser-All" | |
"project": "BVP" | |
"project": "Collectory" | |
"project": "Component-UI" | |
"project": "Dashboard" | |
"project": "f" | |
"project": "FieldCapture" | |
"project": "Geonetwork" | |
"project": "Hubs" | |
"project": "ImageService" | |
"project": "LayerServices" | |
"project": "ListsTool" | |
"project": "ListTool" | |
"project": "NameMatching" | |
"project": "names" | |
"project": "OzAtlasAndroid" | |
"project": "Regions" | |
"project": "Sandbox" | |
"project": "Sighitngs" | |
"project": "Sightings" | |
"project": "SpatialPortal" | |
"project": "WEBAPI" | |
# github api v3 | |
# | |
mbohun@firewolf:~/src> curl --user "mbohun" https://api.github.com/users/mbohun | |
Enter host password for user 'mbohun': | |
{ | |
"login": "mbohun", | |
"id": 1772897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/1772897?", | |
"gravatar_id": "dcdbc4e57c547efe72932b586079d9d6", | |
"url": "https://api.github.com/users/mbohun", | |
"html_url": "https://github.com/mbohun", | |
"followers_url": "https://api.github.com/users/mbohun/followers", | |
"following_url": "https://api.github.com/users/mbohun/following{/other_user}", | |
"gists_url": "https://api.github.com/users/mbohun/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/mbohun/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/mbohun/subscriptions", | |
"organizations_url": "https://api.github.com/users/mbohun/orgs", | |
"repos_url": "https://api.github.com/users/mbohun/repos", | |
"events_url": "https://api.github.com/users/mbohun/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/mbohun/received_events", | |
"type": "User", | |
"site_admin": false, | |
"name": "Martin Bohun", | |
"company": null, | |
"blog": "https://www.google.com/+MartinBohun", | |
"location": "Canberra, ACT, Australia", | |
"email": null, | |
"hireable": true, | |
"bio": null, | |
"public_repos": 14, | |
"public_gists": 54, | |
"followers": 11, | |
"following": 2, | |
"created_at": "2012-05-24T06:28:16Z", | |
"updated_at": "2014-07-21T02:03:43Z", | |
"private_gists": 13, | |
"total_private_repos": 0, | |
"owned_private_repos": 0, | |
"disk_usage": 21889, | |
"collaborators": 0, | |
"plan": { | |
"name": "free", | |
"space": 307200, | |
"collaborators": 0, | |
"private_repos": 0 | |
} | |
} | |
mbohun@firewolf:~/src> | |
# GET all issues for atlasoflivingaustralia biocache-hubs repo | |
mbohun@firewolf:~/src> curl --user "mbohun" https://api.github.com/repos/atlasoflivingaustralia/biocache-hubs/issues | |
Enter host password for user 'mbohun': | |
[ | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/3", | |
"labels_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/3/labels{/name}", | |
"comments_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/3/comments", | |
"events_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/3/events", | |
"html_url": "https://github.com/AtlasOfLivingAustralia/biocache-hubs/issues/3", | |
"id": 38275672, | |
"number": 3, | |
"title": "Add links to associated records", | |
"user": { | |
"login": "nickdos", | |
"id": 532845, | |
"avatar_url": "https://avatars.githubusercontent.com/u/532845?", | |
"gravatar_id": "e836c5faea5deb9e6567db9433628fc2", | |
"url": "https://api.github.com/users/nickdos", | |
"html_url": "https://github.com/nickdos", | |
"followers_url": "https://api.github.com/users/nickdos/followers", | |
"following_url": "https://api.github.com/users/nickdos/following{/other_user}", | |
"gists_url": "https://api.github.com/users/nickdos/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/nickdos/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/nickdos/subscriptions", | |
"organizations_url": "https://api.github.com/users/nickdos/orgs", | |
"repos_url": "https://api.github.com/users/nickdos/repos", | |
"events_url": "https://api.github.com/users/nickdos/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/nickdos/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"labels": [ | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/enhancement", | |
"name": "enhancement", | |
"color": "84b6eb" | |
} | |
], | |
"state": "open", | |
"assignee": { | |
"login": "nickdos", | |
"id": 532845, | |
"avatar_url": "https://avatars.githubusercontent.com/u/532845?", | |
"gravatar_id": "e836c5faea5deb9e6567db9433628fc2", | |
"url": "https://api.github.com/users/nickdos", | |
"html_url": "https://github.com/nickdos", | |
"followers_url": "https://api.github.com/users/nickdos/followers", | |
"following_url": "https://api.github.com/users/nickdos/following{/other_user}", | |
"gists_url": "https://api.github.com/users/nickdos/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/nickdos/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/nickdos/subscriptions", | |
"organizations_url": "https://api.github.com/users/nickdos/orgs", | |
"repos_url": "https://api.github.com/users/nickdos/repos", | |
"events_url": "https://api.github.com/users/nickdos/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/nickdos/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"milestone": null, | |
"comments": 2, | |
"created_at": "2014-07-21T04:16:11Z", | |
"updated_at": "2014-07-21T04:45:03Z", | |
"closed_at": null, | |
"body": "Records that have a duplication_status value do NOT currently link through to the associated records - the record page simply states there are associated records. E.g. http://biocache.ala.org.au/occurrences/34096adc-4d86-4fed-9d56-14d4603d05c4 has:\r\n\r\nAssociated Occurrence Status:\t Representative record\r\n\r\nWe need to create a link to also show a list of all the associated records." | |
} | |
] | |
# POST to create an issue test | |
mbohun@firewolf:~/src> curl --user "mbohun" --request POST --data '{ "title": "only a test issue, created using github api v3 from BASH and curl", "body": "This is the issues body, description, very deep in all important details.", "assignee": "nickdos", "labels": ["Label1", "Label2"] }' https://api.github.com/repos/atlasoflivingaustralia/biocache-hubs/issues | |
Enter host password for user 'mbohun': | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"labels_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/labels{/name}", | |
"comments_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/comments", | |
"events_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/events", | |
"html_url": "https://github.com/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"id": 38279675, | |
"number": 4, | |
"title": "only a test issue, created using github api v3 from BASH and curl", | |
"user": { | |
"login": "mbohun", | |
"id": 1772897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/1772897?", | |
"gravatar_id": "dcdbc4e57c547efe72932b586079d9d6", | |
"url": "https://api.github.com/users/mbohun", | |
"html_url": "https://github.com/mbohun", | |
"followers_url": "https://api.github.com/users/mbohun/followers", | |
"following_url": "https://api.github.com/users/mbohun/following{/other_user}", | |
"gists_url": "https://api.github.com/users/mbohun/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/mbohun/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/mbohun/subscriptions", | |
"organizations_url": "https://api.github.com/users/mbohun/orgs", | |
"repos_url": "https://api.github.com/users/mbohun/repos", | |
"events_url": "https://api.github.com/users/mbohun/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/mbohun/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"labels": [ | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/Label1", | |
"name": "Label1", | |
"color": "ededed" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/Label2", | |
"name": "Label2", | |
"color": "ededed" | |
} | |
], | |
"state": "open", | |
"assignee": { | |
"login": "nickdos", | |
"id": 532845, | |
"avatar_url": "https://avatars.githubusercontent.com/u/532845?", | |
"gravatar_id": "e836c5faea5deb9e6567db9433628fc2", | |
"url": "https://api.github.com/users/nickdos", | |
"html_url": "https://github.com/nickdos", | |
"followers_url": "https://api.github.com/users/nickdos/followers", | |
"following_url": "https://api.github.com/users/nickdos/following{/other_user}", | |
"gists_url": "https://api.github.com/users/nickdos/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/nickdos/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/nickdos/subscriptions", | |
"organizations_url": "https://api.github.com/users/nickdos/orgs", | |
"repos_url": "https://api.github.com/users/nickdos/repos", | |
"events_url": "https://api.github.com/users/nickdos/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/nickdos/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"milestone": null, | |
"comments": 0, | |
"created_at": "2014-07-21T06:48:35Z", | |
"updated_at": "2014-07-21T06:48:35Z", | |
"closed_at": null, | |
"body": "This is the issues body, description, very deep in all important details.", | |
"closed_by": null | |
} | |
# POST to edit/modify an existing issue | |
mbohun@firewolf:~/src> curl --user "mbohun" --request POST --data '{ "title": "Only a TEST issue, created from the commandline using github api v3 from BASH and curl", "body": "see https://gist.github.com/mbohun/af110bcd6e6178b7def3 for beautiful details how this issue was created and edited.", "assignee": "djtfmartin", "labels": ["Label1", "Label2"] }' https://api.github.com/repos/atlasoflivingaustralia/biocache-hubs/issues/4 | |
Enter host password for user 'mbohun': | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"labels_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/labels{/name}", | |
"comments_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/comments", | |
"events_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/events", | |
"html_url": "https://github.com/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"id": 38279675, | |
"number": 4, | |
"title": "Only a TEST issue, created from the commandline using github api v3 from BASH and curl", | |
"user": { | |
"login": "mbohun", | |
"id": 1772897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/1772897?", | |
"gravatar_id": "dcdbc4e57c547efe72932b586079d9d6", | |
"url": "https://api.github.com/users/mbohun", | |
"html_url": "https://github.com/mbohun", | |
"followers_url": "https://api.github.com/users/mbohun/followers", | |
"following_url": "https://api.github.com/users/mbohun/following{/other_user}", | |
"gists_url": "https://api.github.com/users/mbohun/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/mbohun/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/mbohun/subscriptions", | |
"organizations_url": "https://api.github.com/users/mbohun/orgs", | |
"repos_url": "https://api.github.com/users/mbohun/repos", | |
"events_url": "https://api.github.com/users/mbohun/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/mbohun/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"labels": [ | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/Label1", | |
"name": "Label1", | |
"color": "ededed" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/Label2", | |
"name": "Label2", | |
"color": "ededed" | |
} | |
], | |
"state": "open", | |
"assignee": { | |
"login": "djtfmartin", | |
"id": 444897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/444897?", | |
"gravatar_id": "8fccf27675dce1089c7db391650ec09d", | |
"url": "https://api.github.com/users/djtfmartin", | |
"html_url": "https://github.com/djtfmartin", | |
"followers_url": "https://api.github.com/users/djtfmartin/followers", | |
"following_url": "https://api.github.com/users/djtfmartin/following{/other_user}", | |
"gists_url": "https://api.github.com/users/djtfmartin/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/djtfmartin/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/djtfmartin/subscriptions", | |
"organizations_url": "https://api.github.com/users/djtfmartin/orgs", | |
"repos_url": "https://api.github.com/users/djtfmartin/repos", | |
"events_url": "https://api.github.com/users/djtfmartin/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/djtfmartin/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"milestone": null, | |
"comments": 0, | |
"created_at": "2014-07-21T06:48:35Z", | |
"updated_at": "2014-07-21T07:06:08Z", | |
"closed_at": null, | |
"body": "see https://gist.github.com/mbohun/af110bcd6e6178b7def3 for beautiful details how this issue was created and edited.", | |
"closed_by": null | |
} | |
# POST to comment on an issue | |
mbohun@firewolf:~/src> curl --user "mbohun" --request POST --data '{ "body": "This is the very first comment on an issue created from the commandline using the github api v3, ladies and gentlemen." }' https://api.github.com/repos/atlasoflivingaustralia/biocache-hubs/issues/4/comments | |
Enter host password for user 'mbohun': | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/comments/49577117", | |
"html_url": "https://github.com/AtlasOfLivingAustralia/biocache-hubs/issues/4#issuecomment-49577117", | |
"issue_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"id": 49577117, | |
"user": { | |
"login": "mbohun", | |
"id": 1772897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/1772897?", | |
"gravatar_id": "dcdbc4e57c547efe72932b586079d9d6", | |
"url": "https://api.github.com/users/mbohun", | |
"html_url": "https://github.com/mbohun", | |
"followers_url": "https://api.github.com/users/mbohun/followers", | |
"following_url": "https://api.github.com/users/mbohun/following{/other_user}", | |
"gists_url": "https://api.github.com/users/mbohun/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/mbohun/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/mbohun/subscriptions", | |
"organizations_url": "https://api.github.com/users/mbohun/orgs", | |
"repos_url": "https://api.github.com/users/mbohun/repos", | |
"events_url": "https://api.github.com/users/mbohun/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/mbohun/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"created_at": "2014-07-21T07:15:11Z", | |
"updated_at": "2014-07-21T07:15:11Z", | |
"body": "This is the very first comment on an issue created from the commandline using the github api v3, ladies and gentlemen." | |
} | |
# POST to change the label-s of an issue to (one of the predefined labels) "enhancement" | |
mbohun@firewolf:~/src> curl --user "mbohun" --request POST --data '{ "labels": ["enhancement"] }' https://api.github.com/repos/atlasoflivingaustralia/biocache-hubs/issues/4 | |
Enter host password for user 'mbohun': | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"labels_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/labels{/name}", | |
"comments_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/comments", | |
"events_url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/issues/4/events", | |
"html_url": "https://github.com/AtlasOfLivingAustralia/biocache-hubs/issues/4", | |
"id": 38279675, | |
"number": 4, | |
"title": "Only a TEST issue, created from the commandline using github api v3 from BASH and curl", | |
"user": { | |
"login": "mbohun", | |
"id": 1772897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/1772897?", | |
"gravatar_id": "dcdbc4e57c547efe72932b586079d9d6", | |
"url": "https://api.github.com/users/mbohun", | |
"html_url": "https://github.com/mbohun", | |
"followers_url": "https://api.github.com/users/mbohun/followers", | |
"following_url": "https://api.github.com/users/mbohun/following{/other_user}", | |
"gists_url": "https://api.github.com/users/mbohun/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/mbohun/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/mbohun/subscriptions", | |
"organizations_url": "https://api.github.com/users/mbohun/orgs", | |
"repos_url": "https://api.github.com/users/mbohun/repos", | |
"events_url": "https://api.github.com/users/mbohun/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/mbohun/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"labels": [ | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/enhancement", | |
"name": "enhancement", | |
"color": "84b6eb" | |
} | |
], | |
"state": "open", | |
"assignee": { | |
"login": "djtfmartin", | |
"id": 444897, | |
"avatar_url": "https://avatars.githubusercontent.com/u/444897?", | |
"gravatar_id": "8fccf27675dce1089c7db391650ec09d", | |
"url": "https://api.github.com/users/djtfmartin", | |
"html_url": "https://github.com/djtfmartin", | |
"followers_url": "https://api.github.com/users/djtfmartin/followers", | |
"following_url": "https://api.github.com/users/djtfmartin/following{/other_user}", | |
"gists_url": "https://api.github.com/users/djtfmartin/gists{/gist_id}", | |
"starred_url": "https://api.github.com/users/djtfmartin/starred{/owner}{/repo}", | |
"subscriptions_url": "https://api.github.com/users/djtfmartin/subscriptions", | |
"organizations_url": "https://api.github.com/users/djtfmartin/orgs", | |
"repos_url": "https://api.github.com/users/djtfmartin/repos", | |
"events_url": "https://api.github.com/users/djtfmartin/events{/privacy}", | |
"received_events_url": "https://api.github.com/users/djtfmartin/received_events", | |
"type": "User", | |
"site_admin": false | |
}, | |
"milestone": null, | |
"comments": 1, | |
"created_at": "2014-07-21T06:48:35Z", | |
"updated_at": "2014-07-21T07:29:41Z", | |
"closed_at": null, | |
"body": "see https://gist.github.com/mbohun/af110bcd6e6178b7def3 for beautiful details how this issue was created and edited.", | |
"closed_by": null | |
} | |
# GET all labels for atlasoflivingaustralia biocache-hubs | |
mbohun@firewolf:~/src> curl --user "mbohun" https://api.github.com/repos/atlasoflivingaustralia/biocache-hubs/labels | |
Enter host password for user 'mbohun': | |
[ | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/bug", | |
"name": "bug", | |
"color": "fc2929" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/duplicate", | |
"name": "duplicate", | |
"color": "cccccc" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/enhancement", | |
"name": "enhancement", | |
"color": "84b6eb" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/help+wanted", | |
"name": "help wanted", | |
"color": "159818" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/invalid", | |
"name": "invalid", | |
"color": "e6e6e6" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/question", | |
"name": "question", | |
"color": "cc317c" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/wontfix", | |
"name": "wontfix", | |
"color": "ffffff" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/Label1", | |
"name": "Label1", | |
"color": "ededed" | |
}, | |
{ | |
"url": "https://api.github.com/repos/AtlasOfLivingAustralia/biocache-hubs/labels/Label2", | |
"name": "Label2", | |
"color": "ededed" | |
} | |
] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment