Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not all data is exported #21

Closed
JulianKniephoff opened this issue Mar 21, 2017 · 6 comments
Closed

Not all data is exported #21

JulianKniephoff opened this issue Mar 21, 2017 · 6 comments

Comments

@JulianKniephoff
Copy link
Member

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)


Somehow not all data is exported. It is restricted to a start and end-time somehow.


@JulianKniephoff
Copy link
Member Author

Original comment by Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf):


@danielebbert: Could you provide more details on this problem, as we could not reproduce this

@JulianKniephoff
Copy link
Member Author

Original comment by Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff):


Did you test it with the same data set again? Maybe this has to do with encoding or size. I only tested relatively few annotations with very "harmless" contents.

The other thing is probably unrelated, as you said. I'll go ahead and create another issue for that. EDIT: Here it is!

@JulianKniephoff
Copy link
Member Author

Original comment by Matthias Neugebauer (Bitbucket: mtneug, GitHub: mtneug):


Well the data set has grown since then, but the original annotations should still be part of it. The only thing I noticed was an annotation with newlines in it. These are carried over to the CSV file, but I guess this is ok since the whole text is quoted. Apart from that we only testet common German characters as ä, ö, ü, which worked fine. The resulting CSV file contains 270 entries. Querying the database directly (and accounting for deleted annotations) I could confirm this number.

@JulianKniephoff
Copy link
Member Author

Original comment by Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff):


Okay, I'll run another bigger and meaner test myself and see if something comes up. If not, I vote for closing this issue for irreproducability until someone bumps into this again. :)

@JulianKniephoff
Copy link
Member Author

Original comment by Matthias Neugebauer (Bitbucket: mtneug, GitHub: mtneug):


Sounds good. Thanks 👍

@JulianKniephoff
Copy link
Member Author

Original comment by Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff):


Okay even exporting 500+ annotations with line breaks and illegally encoded Umlauts works for me.

@JulianKniephoff JulianKniephoff added this to the 4. Export Options milestone Jan 10, 2018
This was referenced Jan 10, 2018
JulianKniephoff added a commit to JulianKniephoff/annotation-tool that referenced this issue Jan 10, 2018
mliradelc added a commit to mliradelc/annotation-tool that referenced this issue Jun 24, 2019
# This is the 1st commit message:

Add HLS support

Update files from develop branch

Fixed German translation file syntax

Closes opencast#173.

Add Emacs configuration

`npm update && npm audit fix`

Changed `less` plugin for `grunt`

This switches from `assemble-less` to `grunt-contrib-less`
and updates the latter at least a bit,
all in order to get rid of a few security vulnerabilities.
Further updates pending mostly because of incompatibilities.

Updated `grunt-contrib-less` to the latest version

More package updates

# This is the commit message #2:

Removed unused grunt plugin

# This is the commit message #3:

Removed some unused dependencies

# This is the commit message #4:

Improved code quality

# This is the commit message #5:

Removed some dead code and obsolete comments

# This is the commit message #6:

Got rid of `box-sizing`-'polyfill"

Box sizing has good enough support now.
If we still want backwards compat,
I feel like a CSS postprocessor
would be a better approach.

# This is the commit message opencast#7:

Simplified some event handling code

# This is the commit message opencast#8:

Refactored comment model slightly

Comments should be creatable without text.
But I **do** see the problem this brings.
So why not make the empty string the default text? ;)

# This is the commit message opencast#9:

Refactored some view cleanup and deleted related dead code

# This is the commit message opencast#10:

Allowed editing multiple annotations simultaneously

# This is the commit message opencast#11:

Use `maven-enforcer-plugin` instead of `prerequisites`

Fixes opencast#187.

# This is the commit message opencast#12:

Pinned `maven-install-plugin`

Fixes opencast#185.

# This is the commit message opencast#13:

Added an `npm start` script

# This is the commit message opencast#14:

Updated `grunt-cli`

# This is the commit message opencast#15:

Improved code quality

# This is the commit message opencast#16:

Revert back to a stable version of `grunt-cli`

Closes opencast#188.

# This is the commit message opencast#17:

Fix XACML parsing of rules

OAT filters for ACL rules with the wrong tag name "rules" instead of
"Rule".

# This is the commit message opencast#18:

Fix exception during export when no e-mail is set

# This is the commit message opencast#19:

Simplified some of the export functions a bit

# This is the commit message opencast#20:

Remove unused and vulnerable dependency

# This is the commit message opencast#21:

Updated demo link in the README

Changed the README to include a link to a working demo
# This is the commit message opencast#22:

Update README.md
# This is the commit message opencast#23:

Update checkstyle to fix a vulnerability

# This is the commit message opencast#24:

Improve the style of the checkstyle configuration

# This is the commit message opencast#25:

Update `grunt`
JulianKniephoff added a commit that referenced this issue Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

1 participant