backend merge requestshttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests2021-05-10T06:18:50Zhttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/147Feature/#103 increase pipeline performance2021-05-10T06:18:50ZMichelle WeidlingFeature/#103 increase pipeline performance# Feature
## Summary
This MR provides
- a differentiation between unit and integration tests which allows for two separate stages
- changes in the CI images towards more lean Docker images (and thus to a reduced load when creating/exe...# Feature
## Summary
This MR provides
- a differentiation between unit and integration tests which allows for two separate stages
- changes in the CI images towards more lean Docker images (and thus to a reduced load when creating/executing a stage)
## Closes
Closes #103
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/146Feature/#164 annotations html implementation of simple motifs2021-05-10T12:25:50ZMichelle WeidlingFeature/#164 annotations html implementation of simple motifs# Feature
## Summary
This MR introduces an in-memory intermediate format for simple motifs(*) which is produces by the `motifs-expansion.xqm` module.
It detects motifs (encoded as oXygen comment/processing instruction) and converts the...# Feature
## Summary
This MR introduces an in-memory intermediate format for simple motifs(*) which is produces by the `motifs-expansion.xqm` module.
It detects motifs (encoded as oXygen comment/processing instruction) and converts them to `tei:span`.
A simply motif spanning several lines is transformed to several `tei:span` elements which are connected via an ID and the `@next` attribute.
This intermediate format is then used to create an `xhtml:span` when creating the HTML pages in `tei2html.xqm` module, making the motifs findable by the annotation panel.
(*) _simple motifs_ are text passages in which only one motif is present, i.e. a piece of text doesn't have more than one motif. For the complex case cf. #165.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [x] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #164
## Logs and Screenshots
### How the motifs look like in HTML
![Screenshot_2021-05-07_12-32-46](/uploads/fb05d9e057421794f23e5c4bf80d307f/Screenshot_2021-05-07_12-32-46.png)
### AnnotationAPI now considers multi-line motifs in ID creation
![image](/uploads/2fd56ca4d2e1db600694a12a46bc676e/image.png)
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/148fix: add logging when error occurs2021-05-17T06:53:12ZMichelle Weidlingfix: add logging when error occurs# Bug fix
## Summary
Although the error is caused by faulty data, we added some logging to give us more insight about a problem.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [ ] Product Owner ac...# Bug fix
## Summary
Although the error is caused by faulty data, we added some logging to give us more insight about a problem.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [ ] Product Owner accepts the User Story
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Readme and general docs
* [ ] I updated the README (if applicable) and kept the docs up to date.
## Closes
Closes #166
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/151Feature/#167 annotations motifs that span several pages2021-06-02T09:49:17ZMichelle WeidlingFeature/#167 annotations motifs that span several pages# Bug fix
## Summary
The serialization of simple motifs is now able to deal with motifs spanning over a page's end.
Motifs that encompass more than one line are connected via a `data-next` attribute in HTML.
The AnnotationAPI exposes t...# Bug fix
## Summary
The serialization of simple motifs is now able to deal with motifs spanning over a page's end.
Motifs that encompass more than one line are connected via a `data-next` attribute in HTML.
The AnnotationAPI exposes the first part of a motif available on a page.
Furthermore some of the Docker images in the CI config have been exchanged with smaller versions in order to improve performance.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## How to test this fix
- log in to VPN
- go to https://ahikar-test.uni-goettingen.de
- select the manuscript Cod. Arab. 236 Copenhagen
- go to page 6a and see if the HTML is displayed (this might take a while, cf. #159 )
- go to https://ahikar-test.sub.uni-goettingen.de/api/annotations/ahikar/arabic-karshuni/3r177/6a/annotationPage.json and check if there is one motif present
- go to https://ahikar-test.sub.uni-goettingen.de/api/annotations/ahikar/arabic-karshuni/3r177/2b/annotationPage.json and check if there are two motifs present
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Readme and general docs
* [x] I updated the README (if applicable) and kept the docs up to date.
## Closes
Closes #167.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/150Feature/#159 annotations performance2021-06-04T12:49:02ZMichelle WeidlingFeature/#159 annotations performance# Feature
## Summary
This MR provides a solution for making the annotations more performant.
Instead of determining the relevant annotations items on the fly they are now stored in one file per page.
This file is stored in `/db/data/t...# Feature
## Summary
This MR provides a solution for making the annotations more performant.
Instead of determining the relevant annotations items on the fly they are now stored in one file per page.
This file is stored in `/db/data/textgrid/json` and updated by a database trigger each time the respective file gets updated, too.
This MR also contains some fixes in the editorial annotations for that have been discovered during testing the main feature of this branch.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
* [x] Yes, you can test by following these steps:
1. build the database locally
2. publish the Arabic and Karshuni collection to your local database
3. after having published them each page of each TEI document has a `*.json` containing the relevant annotation items in `/db/data/textgrid/json`.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #159.
## Logs and Screenshots
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/153Feature/#170 annotations performance total no of annotations2021-06-07T13:56:57ZMichelle WeidlingFeature/#170 annotations performance total no of annotations# Feature
## Summary
This MR fixes an issue in the computation of the total annotation number per collection/manifest.
While the computation created all annotations before counting them, this approach makes use of the saved annotation...# Feature
## Summary
This MR fixes an issue in the computation of the total annotation number per collection/manifest.
While the computation created all annotations before counting them, this approach makes use of the saved annotation items and adds them up. This saves a lot of time when calling the AnnotationAPI.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #170
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/152Feature/#169 html performance2021-06-07T16:09:05ZMichelle WeidlingFeature/#169 html performance# Feature
## Summary
This MR provides a solution for making the display of HTML pages more performant.
Instead of creating the relevant HTML files on the fly they are now stored in one file per manuscript page and text type. This file...# Feature
## Summary
This MR provides a solution for making the display of HTML pages more performant.
Instead of creating the relevant HTML files on the fly they are now stored in one file per manuscript page and text type. This file is stored in `/db/data/textgrid/html` and updated by a database trigger each time the respective file gets updated.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
* [x] Yes, you can test by following these steps:
1. build the database locally
1. publish the Arabic and Karshuni collection to your local database
1. after having published them each page of each TEI document has a `*.html` serialization in `/db/data/textgrid/html`.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #169 .
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/154feat: remove `total` and `startIndex`2021-06-08T08:42:21ZMichelle Weidlingfeat: remove `total` and `startIndex`# Feature
## Summary
This MR removes the fields `total` and `startIndex` from the AnnotationAPI. The reasons for this decision are:
* Both keys are not mandatory according to the W3C Data Annotation Model
* They aren't used in any of ...# Feature
## Summary
This MR removes the fields `total` and `startIndex` from the AnnotationAPI. The reasons for this decision are:
* Both keys are not mandatory according to the W3C Data Annotation Model
* They aren't used in any of our application
* Depending on the size of the collection they are quite costly to compute
Although we now this might result in some drawbacks when using the annotations in another application outside the SUB (there is no use case for this scenario yet), we decided to opt for a better performance.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [x] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [x] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #172.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/155feat: indicate person responsible for correction2021-06-08T12:53:05ZMichelle Weidlingfeat: indicate person responsible for correction# Feature
## Summary
This MR provides information about the person responsible for a correction in `tei:corr`.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner accepts the User Sto...# Feature
## Summary
This MR provides information about the person responsible for a correction in `tei:corr`.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #173.
## Logs and Screenshots
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/156Feature/#174 performance improve triggers2021-06-10T07:28:32ZMichelle WeidlingFeature/#174 performance improve triggers# Feature
## Summary
This MR provides a slightly different approach to executing the database triggers.
In order to improve their performance, calling `commons:get-page-fragments()` several times per manuscripts has been reduced to ca...# Feature
## Summary
This MR provides a slightly different approach to executing the database triggers.
In order to improve their performance, calling `commons:get-page-fragments()` several times per manuscripts has been reduced to calling it once per document.
This also reduces the calls to `me:main()`, a relatively costly operation, which is called during commons:get-page-fragments().
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #174
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/159Bugfix/#178 fonts are empty2021-06-21T11:17:26ZMichelle WeidlingBugfix/#178 fonts are empty# Bug fix
## Summary
With this MR the fonts are provided as binaries via the TextAPI instead of texts, making them usable again.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner ac...# Bug fix
## Summary
With this MR the fonts are provided as binaries via the TextAPI instead of texts, making them usable again.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner accepts the User Story
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Readme and general docs
* [ ] I updated the README (if applicable) and kept the docs up to date.
## Closes
Closes #178
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/160rename-qviewer-to-tido2021-06-24T10:16:53ZNils Windischrename-qviewer-to-tidohttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/157docs: add CI docs2021-06-25T05:48:05ZMichelle Weidlingdocs: add CI docs# Feature
## Summary
This MR provides a more extensive documentation of all things CI.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] F...# Feature
## Summary
This MR provides a more extensive documentation of all things CI.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [x] Product Owner accepts the User Story
## Documentation
* [x] I adjusted other parts of the documentation (if applicable)
## Tests
* [x] No, it is not possible.
## Closes
Closes #176
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/161Bugfix/#183 item object title wrong cardinality2021-06-25T06:41:09ZMichelle WeidlingBugfix/#183 item object title wrong cardinality# Bug fix
## Summary
With this MR, the XPath for retrieving the title object of an item has been refined.
To check if this has been done correctly, go to https://ahikar-test.sub.uni-goettingen.de/api/textapi/ahikar/arabic-karshuni/3rx...# Bug fix
## Summary
With this MR, the XPath for retrieving the title object of an item has been refined.
To check if this has been done correctly, go to https://ahikar-test.sub.uni-goettingen.de/api/textapi/ahikar/arabic-karshuni/3rx14-3/latest/item.json. This page should A) be available (which hasn't been the case before because of the bug) and B) should the title object have the following form:
```json
"title" : [ {
"title" : "The Story and Proverbs of Ahiqar the Wise",
"type" : "main"
} ]
```
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Readme and general docs
* [x] I updated the README (if applicable) and kept the docs up to date.
## Closes
Closes #183
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/158Bugfix/#171 annotations items provided as object instead of array2021-06-25T11:37:44ZMichelle WeidlingBugfix/#171 annotations items provided as object instead of array# Bug fix
## Summary
This MR considers the case where we have only one annotation item on a page.
While this has been stored as object previously, it is now stored within an array and can be accessed properly by TIDO.
### How to test:...# Bug fix
## Summary
This MR considers the case where we have only one annotation item on a page.
While this has been stored as object previously, it is now stored within an array and can be accessed properly by TIDO.
### How to test:
- go to https://ahikar-test.sub.uni-goettingen.de/api/annotations/ahikar/arabic-karshuni/3r177/6a/annotationPage.json (VPN)
- check if the annotation item is part of an array
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Readme and general docs
* [ ] I updated the README (if applicable) and kept the docs up to date.
## Closes
Closes #171
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/163Feature/#187 udpdate to exist 5 3 02021-07-02T09:55:06ZMichelle WeidlingFeature/#187 udpdate to exist 5 3 0# Feature
## Summary
This MR provides an update to eXist-db 5.3.0 with the necessary changes. According to the [release notes](https://exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb530) the most important changes we have to consider ...# Feature
## Summary
This MR provides an update to eXist-db 5.3.0 with the necessary changes. According to the [release notes](https://exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb530) the most important changes we have to consider are:
- Duplicate functions will reliably throw a useful error
- Made fn:collection spec compliant
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #187
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/162Feature/#179 basic search2021-07-05T19:59:47ZMathias GoebelFeature/#179 basic search# Feature
## Summary
This MR provides a basic search API.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if ...# Feature
## Summary
This MR provides a basic search API.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [ ] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [x] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
* [x] Yes, you can test by following these steps:
```
curl -X POST http://0.0.0.0:49161/exist/restxq/search -H "Content-Type: application/json" -d '{
"query": {
"simple_query_string": {
"query": "Erfa*" }
},
"from": 0,
"size": 3,
"kwicsize": 20
}'
```
* [ ] No, it is not possible.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes
## Logs and Screenshots
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Mathias GoebelMathias Goebelhttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/164feat: update collection title2021-07-06T07:33:42ZMichelle Weidlingfeat: update collection title# Feature
## Summary
This MR provides information about the manuscripts a collection contains in the collection title.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the ...# Feature
## Summary
This MR provides information about the manuscripts a collection contains in the collection title.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
* [ ] Yes, you can test by following these steps:
1. Go to <https://ahikar-test.sub.uni-goettingen.de>. The collection title should be ""
2. Go to <https://ahikar-test.sub.uni-goettingen.de>. The collection title should be ""
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #188
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/167Feature/#84 consider salhani metadata2021-07-09T05:34:42ZMichelle WeidlingFeature/#84 consider salhani metadata# Feature
## Summary
This MR provides the manifest metadata for the Salhani print.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] ...# Feature
## Summary
This MR provides the manifest metadata for the Salhani print.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [ ] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [x] Yes, everything can be done via unit tests.
* [ ] Yes, you can test by following these steps: …
* [ ] No, it is not possible.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes #84.
## Logs and Screenshots
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/subugoe/ahiqar/backend/-/merge_requests/166feat: data import script2021-07-09T15:29:52ZMathias Goebelfeat: data import script# Feature
## Summary
This MR provides a script for importing source data form textgrid. This is useful for checking the application against the source data set.
It also allows to check import timings locally.
## Compliance to “Definit...# Feature
## Summary
This MR provides a script for importing source data form textgrid. This is useful for checking the application against the source data set.
It also allows to check import timings locally.
## Compliance to “Definition of Done”
* [x] Unit tests passed
* [x] Code reviewed
* [x] Product Owner accepts the User Story
## Documentation
* [ ] I updated the README (if applicable)
* [x] I provided my functions with appropriate documentation
* [ ] I updated existing documentation
## Tests
Are we able to test this new feature?
* [ ] Yes, everything can be done via unit tests.
* [ ] Yes, you can test by following these steps: …
* [x] No, it is not possible.
## Changelog
* [x] I added a statement to the CHANGELOG.
## Version number
* [x] I bumped the version number in `build.properties`.
## Closes
Closes
## Logs and Screenshots
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)Mathias GoebelMathias Goebel