You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run a CLAMS app with pretty=true, it should return MMIF files with prettified spacing instead of having all the spaces and line breaks removed.
Reproduction steps
Create a pipeline and a batch with the app called app-swt-detection_par01. This is defined with this endpoint: http://app-swt-detection?pretty=true&sampleRate=500&minFrameCount=5
Run the batch with some asset.
Open resulting MMIF in a text editor.
Expected behavior
Downloaded MMIF files should be the same as the CLAMS app output.
Screenshots
![DESCRIPTION](LINK.png)
Browsers
No response
OS
No response
Additional context
It common for the Clammer and the Brandeis team to open a MMIF file at look at the first 50 or 100 rows, especially the metadata fields. This is very difficult when the formatting is gone.
The text was updated successfully, but these errors were encountered:
Description
When I run a CLAMS app with
pretty=true
, it should return MMIF files with prettified spacing instead of having all the spaces and line breaks removed.Reproduction steps
Create a pipeline and a batch with the app called
app-swt-detection_par01
. This is defined with this endpoint:http://app-swt-detection?pretty=true&sampleRate=500&minFrameCount=5
Run the batch with some asset.
Open resulting MMIF in a text editor.
Expected behavior
Downloaded MMIF files should be the same as the CLAMS app output.
Screenshots
![DESCRIPTION](LINK.png)
Browsers
No response
OS
No response
Additional context
It common for the Clammer and the Brandeis team to open a MMIF file at look at the first 50 or 100 rows, especially the metadata fields. This is very difficult when the formatting is gone.
The text was updated successfully, but these errors were encountered: