Project To Do list

[see24]

Things that should happen before the package/app are used in a production context

• Automate testing to ensure package matches NS with all possible inputs #50
• Do a detailed QA run through of the app
• run R cmd check to check for major errors
• Update help docs and vignettes based on beta tester feedback
• Deal with any bugs deemed necessary definitely:
  Range polygon includes outside NA #34
  Make plot_score_index work better when D score is 0 #45
  Check polygon validity  #43
  Range vs Range clipped to assessment area #37
  Change habitat suitability classification #13

To do before conference to have ready in order of priority

• Could we include multiple CC scenarios #40
• Scenario name needs to match suffix for range change raster #64
• Realistic demo data  #69
• Update the readme (maybe based on poster?)
• Summarize results in report  #18
• Add more clear attribution #14
• Save the csv as backup #56
• Creation of CCEI from scratch #25
• Should there be more help info in the app? #33
• Spatial visualization of results #72

To do before release on CRAN/make public

• confirm with NS/Bruce Young that they are ok with open source release
• Do Open Source Due Diligence ECCC form
• Get R cmd check results up to CRAN standard
• Release ccviR 0.0.0.9004 #52
• Add a vignette for using the package as opposed to the app
• Write a paper introducing it
• Figure out correct logos and attribution text that should be on the app Add more clear attribution #14

On release

• move to LandSciTech organization (might want to do sooner so we can have website while private)
• set up package website (automatically created from help docs and vignette)
• Add a link to the package website "Using the app" article in the Welcome page
• Publicize