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

pull in works and annos from thefinalsclub #13

Open
btbonval opened this issue Apr 1, 2014 · 5 comments
Open

pull in works and annos from thefinalsclub #13

btbonval opened this issue Apr 1, 2014 · 5 comments

Comments

@btbonval
Copy link
Member

btbonval commented Apr 1, 2014

TODO:

Import other sections + ensure the annotation upload is properly aligned for them.
Make filter work so public can see them (See public task)
Preserve legacy information:

  • Annotation types as tags
  • Id of annotation + links to other annotations as object including type of link
@JHilker
Copy link
Member

JHilker commented Apr 1, 2014

Swap uri to be the slug, not the path

Put the annotation in the correct part of the document for legacy annotations

Make documents public on default upload

@JHilker
Copy link
Member

JHilker commented Apr 8, 2014

URI to slug has been completed. Experimental as has an experimental version of displaying the annotations correctly.

@btbonval
Copy link
Member Author

@atrigent has been working on this recently. With the decision to switch away from AnnotationStudio, should we keep this ticket open?

@atrigent
Copy link
Member

Andrew and I decided that I would continue to do this, just so that we have a version of the data which doesn't depend on any PHP weirdness.

@btbonval
Copy link
Member Author

That makes sense.

We'll want to preserve the concepts of the Rails database, but we won't have the same exact data model features like the hierarchy and acts-as-taggable-on. So once we have it in the Rails database, we'll need to do another conversion/import from Rails into Meteor.

I'll look into how close we can get while still being sensible. The easiest thing for conversion would be to mirror the Rails database schema precisely in mongo, but that would almost certainly not be a good idea in the long term for the Annotorious project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants