tei2zenodo issueshttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues2020-07-31T22:53:17Zhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/23populate form fields with defaults taken from server config2020-07-31T22:53:17ZAndreas Wagnerpopulate form fields with defaults taken from server config... rather than hardcode values in index.tmpl ...... rather than hardcode values in index.tmpl ...v0.3 (webservice)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/20Add gitlab config to webform/POST path2020-06-15T07:37:21ZAndreas WagnerAdd gitlab config to webform/POST pathso it's possible to update the repository even if not triggered by webhook.so it's possible to update the repository even if not triggered by webhook.v0.3 (webservice)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/19Add metadata config to webform/POST path2020-06-10T14:19:49ZAndreas WagnerAdd metadata config to webform/POST path... so it's possible to upload something to zenodo via form only without relying on the server config. (Maybe add a checkbox to use the zenodo sandbox or not?)... so it's possible to upload something to zenodo via form only without relying on the server config. (Maybe add a checkbox to use the zenodo sandbox or not?)v0.3 (webservice)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/18Beautify webpage (css)2020-06-10T14:45:28ZAndreas WagnerBeautify webpage (css)what it says...what it says...v0.3 (webservice)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/17Give github better feedback2020-06-10T14:12:06ZAndreas WagnerGive github better feedbackIf we just abort (e.g. because of a bad commit message), github will think the webservice is not working... Look up the specs and how we should be responding.If we just abort (e.g. because of a bad commit message), github will think the webservice is not working... Look up the specs and how we should be responding.BacklogAndreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/14Handle multivolume TEI files2020-06-15T07:33:00ZAndreas WagnerHandle multivolume TEI filesAs the title says. There may be works that are distributed over several files, e.g. [Vitoria's Relectiones](https://id.salamanca.school/texts/W0013):
```xml
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XIncl...As the title says. There may be works that are distributed over several files, e.g. [Vitoria's Relectiones](https://id.salamanca.school/texts/W0013):
```xml
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="W0013">
<teiHeader/>
<text xml:lang="la" type="work_multivolume" xml:id="completeWork">
<group>
<xi:include href="W0013_Vol01.xml" xpointer="Vol01">
<xi:fallback>
<p xml:lang="de">Band 1 konnte nicht eingebunden werden.</p>
</xi:fallback>
</xi:include>
<xi:include href="W0013_Vol02.xml" xpointer="Vol02">
<xi:fallback>
<p xml:lang="de">Band 2 konnte nicht eingebunden werden.</p>
</xi:fallback>
</xi:include>
</group>
</text>
</TEI>
```
It would be desirable to have one deposit per-multivolume work containing several XML files...v0.4 (multifiles)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/11Do things in goroutines2020-06-09T16:13:51ZAndreas WagnerDo things in goroutinesIn order to improve performance, add processing in goroutines.
Possible places:
* [ ] Where multiple files are sent to processing in routing.go, around line 100In order to improve performance, add processing in goroutines.
Possible places:
* [ ] Where multiple files are sent to processing in routing.go, around line 100BacklogAndreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/7Handle other git file change types2020-06-10T07:49:46ZAndreas WagnerHandle other git file change typesCommit messages report, in the `commit.files[x].status` field, what kind of change has happened to the file. Currently, we just ignore `deleted` and `renamed` changes. Should we? Should we handle other change types, too?Commit messages report, in the `commit.files[x].status` field, what kind of change has happened to the file. Currently, we just ignore `deleted` and `renamed` changes. Should we? Should we handle other change types, too?BacklogAndreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/4Sanitize config values2020-06-15T07:32:43ZAndreas WagnerSanitize config values* [ ] Check for sane config values and
* [x] add defaults if no configuration is found.* [ ] Check for sane config values and
* [x] add defaults if no configuration is found.v0.3 (webservice)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/2Add gitlab support2020-06-15T07:32:23ZAndreas WagnerAdd gitlab supportCurrently t2z works with github webhooks. Should it also support gitlab? Several in parallel?Currently t2z works with github webhooks. Should it also support gitlab? Several in parallel?v0.5 (gitlab)Andreas WagnerAndreas Wagnerhttps://gitlab.gwdg.de/rg-mpg-de/tei2zenodo/-/issues/1Add other event types' webhooks2020-06-09T16:13:27ZAndreas WagnerAdd other event types' webhookst2z currently works with github `push` hooks. Maybe we should think of ways in which other events could be put to use, e.g. `release`. Cf. <https://developer.github.com/v3/activity/events/types/>t2z currently works with github `push` hooks. Maybe we should think of ways in which other events could be put to use, e.g. `release`. Cf. <https://developer.github.com/v3/activity/events/types/>BacklogAndreas WagnerAndreas Wagner