You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

137 lines
5.3 KiB

6 years ago
5 years ago
6 years ago
6 years ago
4 years ago
4 years ago
5 years ago
4 years ago
4 years ago
6 years ago
4 years ago
4 years ago
4 years ago
4 years ago
6 years ago
4 years ago
4 years ago
4 years ago
4 years ago
6 years ago
5 years ago
5 years ago
6 years ago
5 years ago
5 years ago
5 years ago
6 years ago
6 years ago
  1. <div align="center">
  2. <img src="./docs/images/logo/doccano.png">
  3. </div>
  4. # doccano
  5. [![Codacy Badge](https://api.codacy.com/project/badge/Grade/98a0992c0a254d0ba23fd75631fe2907)](https://app.codacy.com/app/Hironsan/doccano?utm_source=github.com&utm_medium=referral&utm_content=doccano/doccano&utm_campaign=Badge_Grade_Dashboard)
  6. [![Build Status](https://travis-ci.com/doccano/doccano.svg?branch=master)](https://travis-ci.com/doccano/doccano)
  7. doccano is an open source text annotation tool for humans. It provides annotation features for text classification, sequence labeling and sequence to sequence tasks. So, you can create labeled data for sentiment analysis, named entity recognition, text summarization and so on. Just create a project, upload data and start annotating. You can build a dataset in hours.
  8. ## Demo
  9. You can try the [annotation demo](http://doccano.herokuapp.com).
  10. ![Demo image](./docs/images/demo/demo.gif)
  11. ## Features
  12. - Collaborative annotation
  13. - Multi-language support
  14. - Mobile support
  15. - Emoji :smile: support
  16. - Dark theme
  17. - RESTful API
  18. ## Usage
  19. Two options to run doccano:
  20. - Production
  21. - Development
  22. In any case, you need Docker and Docker Compose. Anyway, you need to clone the repository:
  23. ```bash
  24. $ git clone https://github.com/doccano/doccano.git
  25. $ cd doccano
  26. ```
  27. _Note for Windows developers: Be sure to configure git to correctly handle line endings or you may encounter `status code 127` errors while running the services in future steps. Running with the git config options below will ensure your git directory correctly handles line endings._
  28. ```bash
  29. git clone https://github.com/doccano/doccano.git --config core.autocrlf=input
  30. ```
  31. ### Production
  32. ```bash
  33. $ docker-compose -f docker-compose.prod.yml up
  34. ```
  35. Go to <http://0.0.0.0/>.
  36. Note the superuser account credentials located in the `docker-compose.prod.yml` file:
  37. ```yml
  38. ADMIN_USERNAME: "admin"
  39. ADMIN_PASSWORD: "password"
  40. ```
  41. > Note: If you want to add annotators, see [Frequently Asked Questions](./docs/faq.md)
  42. <!--
  43. ### Docker
  44. As a one-time setup, create a Docker container for Doccano:
  45. ```bash
  46. docker pull doccano/doccano
  47. docker container create --name doccano \
  48. -e "ADMIN_USERNAME=admin" \
  49. -e "ADMIN_EMAIL=admin@example.com" \
  50. -e "ADMIN_PASSWORD=password" \
  51. -p 8000:8000 doccano/doccano
  52. ```
  53. Next, start Doccano by running the container:
  54. ```bash
  55. docker container start doccano
  56. ```
  57. To stop the container, run `docker container stop doccano -t 5`.
  58. All data created in the container will persist across restarts.
  59. Go to <http://127.0.0.1:8000/>.
  60. -->
  61. ### Development
  62. ```bash
  63. $ docker-compose -f docker-compose.dev.yml up
  64. ```
  65. Go to <http://127.0.0.1:3000/>.
  66. ## One-click Deployment
  67. | Service | Button |
  68. |---------|---|
  69. | AWS[^1] | [![AWS CloudFormation Launch Stack SVG Button](https://cdn.rawgit.com/buildkite/cloudformation-launch-stack-button-svg/master/launch-stack.svg)](https://console.aws.amazon.com/cloudformation/home?#/stacks/create/review?stackName=doccano&templateURL=https://s3-external-1.amazonaws.com/cf-templates-10vry9l3mp71r-us-east-1/2019290i9t-AppSGl1poo4j8qpq) |
  70. | Azure | [![Deploy to Azure](https://azuredeploy.net/deploybutton.svg)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fdoccano%2Fdoccano%2Fmaster%2Fazuredeploy.json) |
  71. | GCP[^2] | [![GCP Cloud Run PNG Button](https://storage.googleapis.com/gweb-cloudblog-publish/images/run_on_google_cloud.max-300x300.png)](https://console.cloud.google.com/cloudshell/editor?shellonly=true&cloudshell_image=gcr.io/cloudrun/doccano&cloudshell_git_repo=https://github.com/doccano/doccano.git) |
  72. | Heroku | [![Deploy](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy) |
  73. > [^1]: (1) EC2 KeyPair cannot be created automatically, so make sure you have an existing EC2 KeyPair in one region. Or [create one yourself](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#having-ec2-create-your-key-pair). (2) If you want to access doccano via HTTPS in AWS, here is an [instruction](https://github.com/doccano/doccano/wiki/HTTPS-setting-for-doccano-in-AWS).
  74. > [^2]: Although this is a very cheap option, it is only suitable for very small teams (up to 80 concurrent requests). Read more on [Cloud Run docs](https://cloud.google.com/run/docs/concepts).
  75. ## Contribution
  76. As with any software, doccano is under continuous development. If you have requests for features, please file an issue describing your request. Also, if you want to see work towards a specific feature, feel free to contribute by working towards it. The standard procedure is to fork the repository, add a feature, fix a bug, then file a pull request that your changes are to be merged into the main repository and included in the next release.
  77. Here are some tips might be helpful. [How to Contribute to Doccano Project](https://github.com/doccano/doccano/wiki/How-to-Contribute-to-Doccano-Project)
  78. ## Citation
  79. ```tex
  80. @misc{doccano,
  81. title={{doccano}: Text Annotation Tool for Human},
  82. url={https://github.com/doccano/doccano},
  83. note={Software available from https://github.com/doccano/doccano},
  84. author={
  85. Hiroki Nakayama and
  86. Takahiro Kubo and
  87. Junya Kamura and
  88. Yasufumi Taniguchi and
  89. Xu Liang},
  90. year={2018},
  91. }
  92. ```
  93. ## Contact
  94. For help and feedback, please feel free to contact [the author](https://github.com/Hironsan).