https://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112020-10-22T12:01:16ZRedmineOpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=66472020-10-22T12:01:16ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/1398">Feature #1398</a>: Compress SQL export files</i> added</li></ul> OpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=69932021-03-26T11:19:51ZBernhard Koschiček-Krombholz
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>In Progress</i></li></ul> OpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=69942021-03-26T11:28:56ZBernhard Koschiček-Krombholz
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/6994/diff?detail_id=9087">diff</a>)</li></ul><p>Single entity export in csv is now possible. <br />The API Endpoint is <em>/entity</em> with the parameter <em>?export=csv</em> (e.g. /api/0.2/entity/19947?export=csv)</p>
<p>Also a button was added for the entity view if the API module is activated.</p>
Currently are these field available:
<ul>
<li>id</li>
<li>name</li>
<li>description</li>
<li>begin_from</li>
<li>begin_to</li>
<li>begin_comment</li>
<li>end_from</li>
<li>end_to</li>
<li>end_comment</li>
<li>cidoc_class</li>
<li>system_class</li>
<li>note</li>
<li>geom_type</li>
<li>coordinates</li>
</ul>
Additionally, all linked entities and types are summarized under the type name and separeted by |, e.g.:
<ul>
<li>has_type: Deserted Village: agridion, selište | Ethnonym of the Vlachs</li>
<li>is_identified_by: Grammos | Gramosta | Gramostea | Gramoz | Gramozi | Γραμμουστα | Γραμος | Грамос</li>
<li>is_referred_to_by: Court Register of Sicil 1622 | Register of nahie Chroupichta 1568/69 I. | Register of nahie Chroupichta 1568/69 II. | Register of nahie Chroupichta 1568/69 III</li>
</ul>
<p>I would appreciate feedback, if this is useful and if other information should be included.</p> OpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=69972021-03-26T12:25:01ZBernhard Koschiček-Krombholz
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/6997/diff?detail_id=9090">diff</a>)</li></ul> OpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=70012021-03-27T13:56:17ZBernhard Koschiček-Krombholz
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/7001/diff?detail_id=9093">diff</a>)</li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>Target version</strong> changed from <i>208</i> to <i>6.1.0</i></li></ul><p>Now also code, system_class and cidoc_class can be exported into csv.</p>
<p>Next steps would be to make modifications to the UI, so a user can use the functions.</p>
<p>All these endpoints also supports the common API parameter, like sorting, filtering, limiting the result etc. With this it could be possible to build dropdown menus for the user to select their wishes.</p> OpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=70052021-03-30T10:40:54ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul></ul><p>Can this be closed? Just asking because it's already in 6.1.0 of roadmap.</p> OpenAtlas - Feature #1402: API: CSV export in APIhttps://redmine.openatlas.eu/issues/1402?journal_id=70082021-03-30T10:55:39ZBernhard Koschiček-Krombholz
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>From the API point of view, yes, if we can agree, that the existing export stays as it is. I can make a new ticket for the UI implementation.</p>