Coder Social home page Coder Social logo

fireproofbox-standard's Introduction

fireproofbox-standard

The standard for keeping track of things in the fireproof box.

With Docker

docker build -t ods/fireproofbox .
docker run -ti -v /path/to/fireproofbox-standard/:/app ods/fireproofbox

Build docs

To build the Sphinx docs in the Docker container:

cd docs/
make html

Static files are in _build directory.

With Vagrant

vagrant up
vagrant ssh
build-sphinx

Then browse to http://localhost:8080/

When in the vagrant shell, jsonschema and flatten-tool are also available. You will find your working files in /vagrant.

To exit:

exit
vagrant halt

fireproofbox-standard's People

Contributors

odscjames avatar rhiaro avatar bibianac avatar

Watchers

Bee Webb avatar James Cloos avatar  avatar  avatar

fireproofbox-standard's Issues

Should we have some way of tracking when things can be destroyed?

eg "Fred has left, in 3 years time we can destroy his right to work checks. Mark that we can destroy these documents after this date." (I'm not sure if it is 3 years, just an example)

Or maybe the other way round, if something has to be kept maybe track the reasons it should be kept?

Can't get flatten-tool to make an csv of example1.csv

vagrant@ubuntu-xenial:/vagrant$ flatten-tool flatten  -f csv -o standard/example1.csv   standard/example1.json 
Traceback (most recent call last):
  File "/usr/local/bin/flatten-tool", line 6, in <module>
    exec(compile(open(__file__).read(), __file__, 'exec'))
  File "/vagrant/src/flattentool/flatten-tool", line 3, in <module>
    flattentool.cli.main()
  File "/vagrant/src/flattentool/flattentool/cli.py", line 212, in main
    flatten(**kwargs_from_parsed_args(args))
  File "/vagrant/src/flattentool/flattentool/__init__.py", line 69, in flatten
    parser.parse()
  File "/vagrant/src/flattentool/flattentool/json_input.py", line 98, in parse
    root_json_list = path_search(self.root_json_dict, self.root_list_path.split('/'))
  File "/vagrant/src/flattentool/flattentool/input.py", line 794, in path_search
    nested_dict[parent_field] = OrderedDict()
TypeError: list indices must be integers or slices, not str

It seems to not like the list being the root element.

If we change the sample so it's in a key called "main"


{"main":[
  {
    "id": "id1",
    "title": "Passport Check for James",
    "date_added": "2018-02-13"
  },
  {
    "id": "id2",
    "title": "Insurance certificate",
    "date_added": "2016-01-13"
  }
]
}

It flattens fine.

Currently reading docs to work out .....

Should we have some way of saying what type of thing it is?

Also discussed was that it might not be documents - the electronic security bank fob was mentioned as a non-paper thing that might go in.

eg "paper", "key fob"

Or maybe go further and say what is on document?

eg "Passport photocopy", "Visa photocopy"

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.