Final animaltracking sample with clientCfg.json in new dir and update…

…d README

Signed-off-by: Paul O'M <mahoney@uk.ibm.com>

LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.

README.md

@@ -0,0 +1,117 @@
+# Animal Tracking Sample
+
+## Overview
+
+<img src="./img/README-animaltracking.png" title="Animal Tracking" alt="Animal Tracking graphic" style="height:70px;">
+
+
+This Animal Tracking Package, written in Typescript, is based on the new Hyperledger Fabric 1.4 programming model, is an 'intermediate' level sample of writing a smart contract for an Animal Tracking blockchain network. It has a range of 'typical' transaction types, with varying parameters and functional checks in context, by way of example. It also has 3 'everyday' query transaction types: history, ownership and ad-hoc query functions eg: find records of a certain transaction type + particular species.
+
+There is a tutorial (soon to be published) that accompanies this contract/client apps - currently it is here -> https://github.com/mahoney1/docs/blob/master/animaltracking-tutorial.md
+
+The smart contract, when deployed,  allows participating organisations (some of whom could be those listed below) to submit different transactions (and depending on who is issuing the identities), according to their organisational role / contractual engagement in the network. The sample can be run using one or two organisations too (as provided to VSCode's local Fabric, or using a network taken from Fabric Samples for which a connection file is built) because this is typically what you will do when you set up your local Fabric for development/testing etc). Participating parties (entities, organisations) can potentially be:
+
+  * **Co-operatives** - responsible for Farms and associated parties in a region - the subject of this tutorial (via application, infrastructure)
+  * **Farmers** (via application, no infrastructure) - responsible for acquisition, selling, movements, animal welfare on a holding.
+  * **Vets** (ditto) - administer healthchecks, medications, administer vaccines if required by an animal.
+  * **Abbatoirs** (ditto) -  complete an animal lifecycle (by a strange twist of fate!), record of movement in/out, purging process etc.
+  * **Regulator** eg. Defra, Gov.UK  (infrastructure) - track the animal's tracking history, from birth to .... retirement !
+  * **Other Goverment Bodies** eg British Cattle Movement Service, also keep records of tracking data of cattle (infrastructure)
+
+and potentially others too can access to query/report via client applications.
+
+  * **Animal Husbandry Association** - for animal welfare (infrastructure potentially or access via Gov gateway apps)
+  * **Society for Animal Science** - for animal science (infrastructure potentially or access via Gov gateway apps)
+
+There are 2 Typescript directories, with the same data model file (under the contracts folder) of:
+  * the Smart Contract (contract)
+  * the client application (client)
+
+## General Flow
+
+The diagram below gives a general overview of the 'tracking lifecycle' in terms of transaction and query lifecycle implemented in the smart contract.
+
+<img src="./img/animaltrackingcontract.png" title="Animal Tracking" alt="Animal Tracking Contract Transaction Flow">
+
+## Transactions (Commit)
+
+The smart contract can be invoked through the **IBM Blockchain Platform VS Code extension**  (after instantiating the contract on the channel, you will have a list of transactions (that require parameters) to submit from the IBM Blockchain extension sidepanel) - or - it can be invoked using the appropriate client applications too (under , `typescript/client/lib` subdirectory) that you'll have downloaded when you clone(d) the Github repo.
+
+The list of transactions are below - if submitting these from the VSCode extension, see comments on supplying parameters below and submit then in the order shown - obviously purge will delete the key (so you may not want to do that yet), but will obviously leave the key's history for querying etc etc:
+
+  * register    - provide the data parameters (each in quotes), separated by a comma as shown 
+                  `["SHEEPGOAT", "000011", "24/07/2019", "BOVIS_ARIES", "FARMER.JOHN", "AVONDALE.LOC1", "ARRIVAL_AV1", "IN_FIELD", "WOOL", "false"]`
+
+                  
+  * depart      - provide 2 data parameters separated by a 'comma' - species, id  Eg. `["SHEEPGOAT", "0009"]`
+
+  * arrive      - provide 4 data parameters separated by a 'comma' - species, id, location, owner Eg. `["SHEEPGOAT", "0009", "AVONDALE.LOC1", "FARMER.JUDE"]`
+
+  * quarantine  - provide 2 data parameters separated by a 'comma' - species, id  Eg. `["SHEEPGOAT", "0009"]`
+
+  * assigninspection  - provide 3 data parameters separated by a 'comma' - species, id, vetId  Eg. `["SHEEPGOAT", "0009","VET001"]`
+
+  * certify  - provide 2 data parameters separated by a 'comma' - species, id  Eg. `["SHEEPGOAT", "0009"]`
+
+  * move  - move within holding (eg farm) - provide 2 data parameters separated by a 'comma' - species, id  Eg. `["SHEEPGOAT", "0009"]`
+
+  * purge  - purge animal eg. visit to abbatoir :-)  - provide 2 data parameters separated by a 'comma' - species, id  Eg. `["SHEEPGOAT", "0009"]`
+
+
+## Transactions (Query)
+
+There are 3 further sample transactions, that perform queries - these do not update the ledger, just queries:
+
+  * queryHist  - provide 2 data parameters separated by a 'comma' - species, id  Eg. `SHEEPGOAT, 000011`
+
+  * queryByOwner  - provide 1 data parameter - owner  Eg. `FARMER.JUDE`
+
+  * queryAdHoc  - provide 1 data parameter - a mango query string that's submitted (eg. `selector:{class: AnimalClass, species: 'SHEEPGOAT'}` )  and returns results of the ad-hoc query string
+
+  * queryBySGRegistrations - no parameters - the CouchDB selector is built in the query.ts file Eg. 'SHEEPGOAT','register'
+
+
+## Client side Typescript app scripts
+
+In the `animaltracking/typescript/client/lib` directory are the client SDK app scripts to invoke transactions, or run the query scripts (the compiled JS that is) as per the tutorial.
+
+These app scripts use the file `animaltracking/typescript/client/cfg/clientCfg.json` as the configurable settings to customise it to your own environment (obviously, the accompanying tutorial uses the defaults provided). 
+
+Node JS uses the relative path to the config file, when you run the client apps.
+
+The file `clientCfg.json` controls things like 'which wallet to use', 'which environmment', 'which identity', 'which Fabric channel' etc etc. 
+
+
+## Running the Typescript examples
+
+### How to clone this repo
+
+1. git clone https://github.com/mahoney1/animaltracking
+
+### initial setup
+
+If you haven't done so already you need to install typescript and optionally tslint into your global npm modules
+- npm install -g typescript
+- npm install -g tslint
+
+### prepare the contract (the IBP extension will do this for you FYI)
+- change to the `animaltracking/typescript/contract` directory
+- run `npm install` to install the dependent node modules
+- run `npm run build` to compile the typescript to javascript
+
+### prepare the client app
+- change to the `animaltracking/typescript/client` directory
+- run `npm install` to install the dependent node modules
+- run `npm run build` to compile the typescript to javascript
+
+### set up a running Fabric with the contract
+Now you need to deploy the contract to a running Fabric. There are many ways this could be done. I would recommend the IBM Blockchain Platform VSCode extension, which sets up a local fabric for you (if you haven't got one). I've provided a link to the [VSCode marketplace](https://marketplace.visualstudio.com/items?itemName=IBMBlockchain.ibm-blockchain-platform)
+
+### to run
+
+Having run the `setupdemo` transaction (no parameters required for local Fabric), it will populate some data on the ledger.
+
+To query the data, run: (`cd to animaltracking/typescript/client/lib`):
+
+`node ./query.js` - runs the query app client to execute query transactions defined in QueryClient.ts (.js compiled from equivalent .ts file)
+