Merge pull request #107 from ccmdesign/ccmd-frontend

Update frontend

Author: Bjwebb

.gitignore

@@ -7,3 +7,4 @@ __pycache__
 media
 .coverage
 htmlcov
+.DS_Store

CONTRIBUTING.md

@@ -17,7 +17,7 @@ Everything we are working on, or considering, is kept in GitHub issues.
 
 If you are able to work with GitHub then please "Create an issue"
 
-Before creating a new issue check to see if the issue already exists. If not, then please do report it. If you have permissions to assign the issue to people and milestones then try to select suitable options. 
+Before creating a new issue check to see if the issue already exists. If not, then please do report it. If you have permissions to assign the issue to people and milestones then try to select suitable options.
 
 If you are not comfortable working with GitHub, but would still like to contribute, then talk to us.  Details at: https://github.com/opendataservices
 
@@ -29,11 +29,11 @@ In order to be clear with everyone involved about how code (and documentation) c
 
 The agreements we use allow the contributor to retain copyright over their contributions, while also granting us the rights to re-licence the projects in future without having to track down each contributor and ask for their agreement.
 
-We also stipulate that, should we re-licence a project, then we will only do so under an approved Open Source Institute licence.  
+We also stipulate that, should we re-licence a project, then we will only do so under an approved Open Source Institute licence.
 
 It also protects us, by requiring contributors to check and confirm that they own the copyright on the contributions they make - this can help keep everything clear when, for example, a contribution is made on employers time.
 
-What this doesn't give us is the right to go out and fight copyright infringements on a contributor's behalf. 
+What this doesn't give us is the right to go out and fight copyright infringements on a contributor's behalf.
 
 Our agreements are built of the templates provided by http://contributoragreements.org/
 
@@ -43,11 +43,11 @@ Before contributions to any of our projects are accepted, we require you to comp
 
 ### Submission Instructions
 
-We have a [generic agreement](http://contributoragreements.org/u2s/bm1v4q5je) that covers all code projects in the [Open Data Services GitHub Organisation](https://github.com/opendataservices)
+We have a [generic agreement](http://contributoragreements.org/u2s/bm1v4q5je) that covers all code projects in the [Open Data Services GitHub Organization](https://github.com/opendataservices)
 
 If this is amenable to you, feel free to complete it. We will be automatically notified that you have submitted an agreement and will contact you (usually in the same day, but in no more than 3 working days)
 
-However, we're more than happy to talk, so if you want to get in touch before you sign anything, then please do. 
+However, we're more than happy to talk, so if you want to get in touch before you sign anything, then please do.
 
 You can contact us at [email protected]
 
@@ -71,7 +71,7 @@ Once we have reviewed and signed a copy of the agreement we will be able accept
 
 ### Bitesize issues
 
-Getting started on someone else's software project can be daunting. So when we have an issue that we think would be a good task for someone new to the project, we mark them as  Bitesize.  
+Getting started on someone else's software project can be daunting. So when we have an issue that we think would be a good task for someone new to the project, we mark them as  Bitesize.
 
 Look for issues marked with the [Bitesize](https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aopendataservices+label%3ABitesize) label if you want somewhere to start.
 

README.md

@@ -1,48 +1,48 @@
 # Org-ID: A list of lists
 
-We are creating a simple proces, tool and codelist to enable data publishers and users to create and use joined up data that identifies organisations. 
+We are creating a simple proces, tool and codelist to enable data publishers and users to create and use joined up data that identifies organizations.
 
 This involves
 
-* Maintaining an list of organisation identifier lists;
+* Maintaining an list of organization identifier lists;
 * Developing a methodology for updating the list
 * Providing simple lookup tools, and guidance on choosing the best identifiers to use
 
-## The register of organisation identifier lists
+## The register of organization identifier lists
 
-An organisation identifier list is any list that contains at least an identifier, and a name, for a collection of organisations. 
+An organization identifier list is any list that contains at least an identifier, and a name, for a collection of organizations.
 
-Building on the [IATI Organisation Registration Agency codelist](http://iatistandard.org/202/codelists/OrganisationRegistrationAgency/) we are creating an updated register of organisation identifier lists.
+Building on the [IATI Organization Registration Agency codelist](http://iatistandard.org/202/codelists/OrganisationRegistrationAgency/) we are creating an updated register of organization identifier lists.
 
-This list will contain detailed meta-data on the nature of the identifiers provided, the coverage of identifier lists. It will provide a unique code to identify each list. 
+This list will contain detailed meta-data on the nature of the identifiers provided, the coverage of identifier lists. It will provide a unique code to identify each list.
 
 This code can be used as a prefix to create simple identifier strings, or can be used as the 'scheme' in a two-part identifier.
 
 ### For example:
 
-The code for the organisation identifier list provided by UK Companies House is 'GB-COH'. The identifier assigned to Open Data Services Co-operative Ltd in this list is '09506232'. Putting this together allows a dataset to unambiguously identify Open Data Services Co-operative Ltd as:
+The code for the organization identifier list provided by UK Companies House is 'GB-COH'. The identifier assigned to Open Data Services Co-operative Ltd in this list is '09506232'. Putting this together allows a dataset to unambiguously identify Open Data Services Co-operative Ltd as:
 
-GB-COH-09506232 
+GB-COH-09506232
 
 or in a table such as:
 
-| Organisation ID Scheme | Organisation ID |
+| Organization ID Scheme | Organization ID |
 |------------------------|-----------------|
 | GB-COH                 | 09506232        |
 
 ### Developing the list of lists
 
 We are prototyping our updated register on GitHub: you can find codelists in the ```/codes/``` directory.
 
-These are structured based on the ```list-schema.json``` JSON Schema in the ```/schema/``` directory. 
+These are structured based on the ```list-schema.json``` JSON Schema in the ```/schema/``` directory.
 
 We have imported codes from a range of sources, and have been updating these [based on the process in our Researchers Handbook](https://docs.google.com/document/d/1lkLjHxXaH9GuAR_g-pv9Qru28f1EeOMZtwXduVboMa4/edit#).
 
 Only those entries with a ```"confirmed":true``` have been reviewed and should be relied upon. All others should be treated as provision.
 
 #### Help us out
 
-Pull requests to update any codes, or suggest new codes are welcome. 
+Pull requests to update any codes, or suggest new codes are welcome.
 
 
 ## List Finder Django App
@@ -69,11 +69,11 @@ python manage.py runserver
 
 ## Tools
 
-### Setup 
+### Setup
 
-The scripts in tools/ have a number of requirements. 
+The scripts in tools/ have a number of requirements.
 
-Set-up a virtual environment to easily install these. 
+Set-up a virtual environment to easily install these.
 
 ```
 virtualenv --python=/usr/local/bin/python3 .ve