Git Product home page Git Product logo

range-ios's Introduction

Lifecycle:Retired

About My Range Application (MyRA) for iOS (iPad)

Alt Text

The Range Mobile Pathfinder project is developing a suite of applications to support the sustainable management of rangelands in British Columbia. Learn more about the Range Program

The goal is to move important crown land management documents from paper to digital, and to make this information accessible in the field through disconnected mobile devices. This also supports a new and consistent process for Range staff across the province to support decision making processes.

An Agile Scrum team is developing the Alpha product to test basic fuctions after March 31, 2018. Future releases will lead towards an application that can be used by staff and public range use agreement holders, on multiple platforms.

For the Alpha Release, the iOS application documented here will allow Range Branch Staff to create a new Range Use Plan (RUP) associated with an existing tenure agreement. The application will pull basic existing information from a database and will allow for the contribution of new information while the app is online or offline. If offline, the data will be stored locally, and synched with the database when connected.

Related MyRA Documentation

Features

Create and edit RUPs (Range Use Plans)

Alt Text

Add Pastures and Schedules to a RUP

Alt Text

Synchronize changes

Alt Text

How to Contribute

If you are including a Code of Conduct, make sure that you have a CODE_OF_CONDUCT.md file, and include the following text in here in the README: "Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms."

License

Detailed guidance around licenses is available here

Attach the appropriate LICENSE file directly into your repository before you do anything else!

The default license For code repositories is: Apache 2.0

Here is the boiler-plate you should put into the comments header of every source code file as well as the bottom of your README.md:

Copyright 2015 Province of British Columbia

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at 

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

For repos that are made up of docs, wikis and non-code stuff it's Creative Commons Attribution 4.0 International, and should look like this at the bottom of your README.md:

Creative Commons Licence
YOUR REPO NAME HERE by the Province of Britich Columbia is licensed under a Creative Commons Attribution 4.0 International License.

and the code for the cc 4.0 footer looks like this:

<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons Licence"
style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/80x15.png" /></a><br /><span
xmlns:dct="http://purl.org/dc/terms/" property="dct:title">YOUR REPO NAME HERE</span> by <span
xmlns:cc="http://creativecommons.org/ns#" property="cc:attributionName">the Province of Britich Columbia
</span> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">
Creative Commons Attribution 4.0 International License</a>.

range-ios's People

Contributors

amirshayegh avatar heatherremacle avatar jleach avatar lmullane avatar micheal-w-wells avatar repo-mountie[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

ashayegh

range-ios's Issues

Allow updates to PLD %

PLD % are a new thing and will need to be tweaked, write once then read only does not allow for any adjustment.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Plans in both iOS and web showing previous clients after FTA client updates change

Background

  • agreement holders change by way of a disposition
  • when the disposition is complete staff update FTA to reflect the new agreement holders
  • if a new plan is needed as a result of client changes staff can initiate an amendment so the need for signatories is triggered
  • identified by Kassia James on RAN076112 (2019-03-15)

Requirements-General

  • only current agreement holders/partners should show up on current/editable plans
  • former agreement holders must be identified and shown as having signed on the plans to which they were signatories
  • once a plan is approved (signed by all) it should not longer "accept" FTA update changes to data
  • when an approved plan enters (or remains in) any editable status (ex. by way of amendment) "FTA current" data needed

Requirements-Specific

  • current clients pulled into system using initial data pull from FTA, identified using Client# and locn code and visible on pertinent RANs
  • on subsequent data pulls current vs. previous and main vs. joint venture partner status must be updated
  • agreement holders displayed consistent with Requirements-General

AUM usage for 'past agreement date RUPs'

A need to have plan dates extending past agreement dates for some renewals means that the AUM Usage information will have a gap (from date of agreement end to plan end date). This issue is to track the work on the solution to extend usage data past what FTA sends to MyRangeBC.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Add missing topics

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

add a topic

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip ๐Ÿค“

  • If your org is not in the list below, or the table contains errors, please create an issue here.

  • While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

  • Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

  • If your application is live, add the production URL.

Ministry Short Codes

Short Code Organization Name
AEST Advanced Education, Skills & Training
AGRI Agriculture
ALC Agriculture Land Commission
AG Attorney General
MCF Children & Family Development
CITZ Citizens' Services
DBC Destination BC
EMBC Emergency Management BC
EAO Environmental Assessment Office
EDUC Education
EMPR Energy, Mines & Petroleum Resources
ENV Environment & Climate Change Strategy
FIN Finance
FLNR Forests, Lands, Natural Resource Operations & Rural Development
HLTH Health
FLNR Indigenous Relations & Reconciliation
JEDC Jobs, Economic Development & Competitiveness
LBR Labour Policy & Legislation
LDB BC Liquor Distribution Branch
MMHA Mental Health & Addictions
MAH Municipal Affairs & Housing
BCPC Pension Corporation
PSA Public Safety & Solicitor General & Emergency B.C.
SDPR Social Development & Poverty Reduction
TCA Tourism, Arts & Culture
TRAN Transportation & Infrastructure

NOTE See an error or omission? Please create an issue here to get it remedied.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 392 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

As a staff person I want to create a future RUP for an agreement that already has an approved RUP so that the approved RUP will be in place in a timely fashion

See #156 for background on the time considerations when preparing RUPs
See bcgov/range-api#56 for general info on versioning
Where an existing plan is already in place a situation may arise where:

  • approved version of the plan exists
  • staff starts "next-plan" preparation
  • "next-plan" may be signed by agreement holder AND decision maker but does not become "current-plan" until "current-plan" term ends (becoming "former-plan") and

Functional Plan Types (NB related to system statuses but does not capture all of those needed )

  • "current-plan" -- plan is signed by all parties and is current legal version
  • "next-plan-draft" -- plan start date in the future -- not yet signed by all
  • "next-plan-approved" -- plan start date in the future -- all parties have signed
  • "former-plan" -- a plan that was "current-plan" exceeds it's original expiry (or extended plan end date) and is no longer legal

Requirements

  • staff can start a next-plan-draft from scratch
  • staff can start a next-plan-draft making full copy from "current-plan" except usage and yearly schedules data (most likely workflow)
  • usage data should populate all available years data from FTA and populate any years outside of current term with final year of agreement data
  • staff and agreement holders complete all tasks from draft through approved including considering #156 (plan date(s) extend beyond current agreement expiry)
  • next-draft plan status clearly visible as being "NEXT" and whatever status is (ex. awaiting feedback, or submitted for review or decision)
  • approved next-plan keeps "next-plan" status until "current-plan" reaches expiry becoming "former-plan" and "next-plan's" start date is reached

app store pipeline broken

`"[20:48:32]: Login successful

[!] Couldn't find app 'ca.bc.gov.myrangebc' on the account of '***' on App Store Connect
##[error]Error: fastlane failed with return code: 1"`

@jleach if you get time soon can you help me look at this? I can't access the azure pipeline ( don't think) to address it and I have some stuff I need to get in to test.

As a staff person I want to create a RUP with a plan end date beyond the current agreement expiry date so that pre-decision processes (ex. consultation) and approval can be complete before livestock turnout

Explanation

  • grazing agreements are replaceable meaning it is unusual for a plan not to be replaced for an additional term at the time of expiry
  • staff must work on the assumption that the agreement WILL be replaced
  • before a RUP can be signed by the decision maker it must go through extensive consultative (and other) processes which take time
  • waiting until agreements ARE replaced (always on January 1st of the year following expiry) does not allow sufficient time for those processes and decision making before turn out -- and a RUP must be in place at time of turnout
  • the processes of preparing a new RUP for approval must begin before the agreement expires even though the new RUP in question may have one or both of plan start and end date beyond current agreement expiry

Considerations

  • key data in RUPs is pulled from FTA -- most notably the usage data
  • usage data is relatively stable but can change somewhat over time (ex. non-use, temporary increase, or permanent allocation change)
  • usage data does not exist in FTA for dates beyond the current agreement expiry -- usually entered early January following expiry
  • annual usage data is an essential part of the RUP and critical for an agreement holder preparing schedules
  • the last year of the current agreement term (meaning the year of expiry) is more often than not the usage that will continue for the foreseeable future -- but as noted above that may not be the case if the final year reflects a non-use or temporary increase
  • the final year of the agreement AUM allocation (usage) may be use to populate all upcoming years (we'll call that post-expiry data) in the new RUP recognizing that:
    - staff may need to overwrite that data if final year is mid-stream in a non-use or temp increase
    - FTA will need to overwrite the post-expiry data once the replaced agreement and usage has been entered in FTA
    - there is potential at the time of overwrite that the FTA data differs from the data entered in by staff therefore the differences need to be identified and staff will need to knows what they need to address

Sub-elements

  • staff generate new RUP with date(s) extending past agreement expiry
  • system populates all post-expiry usage data with the AUMs from the final agreement year #152
  • staff can overwrite the usage data for specific years
  • at time of FTA data update post-expiry usage data overwritten with FTA-current data
  • staff are notified if any FTA-current data differed from post-expiry data
  • staff can enter amendment process to update data if needed

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 390 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 391 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

needs new date picker

RO (Range officers) need dates as much as 25 years in the future and current custom date picker is cumbersome for far reaching dates, also it renders many times on load.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.