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

Fslite stage2 #102

Closed
wants to merge 52 commits into from
Closed

Fslite stage2 #102

wants to merge 52 commits into from

Conversation

ximenesuk
Copy link
Contributor

There's still plenty to do on this but it would be good to get it into some build and working with Insight.

A handful of file formats including SPW, big image and multi-image formats import okay in local testing of cli and dropbox import. Areas that definitely need attention (beyond integration with GUI importers):

  • thumbnails in multi-image formats (last in series is used by default?)
  • refactoring of repository services
  • complete overhaul of import tests
  • no performance testing has been done
  • ...and lots more!

Colin Blackburn and others added 30 commits February 22, 2012 11:17
writeBlock also added to support testing though might be useful in later workflow.
Remove fslite, dropbox and import options -y and -z used for testing.
Use isMetadataOnly and add import option -m for metadata-only (DropBox).
@joshmoore
Copy link
Member

@jburel , you ok to add this to all future merge-blues? Are you planning any for the moment, or with multi-group merged has that slowed down?

@jburel
Copy link
Member

jburel commented Feb 29, 2012

@joshmoore: I am planning to start working on that tomorrow.

@ximenesuk
Copy link
Contributor Author

The following tickets referring to specific file formats have been covered under the more general fs-lite work:
→ Task #7227: FS-lite: to support Zeiss LSM
→ Task #7232: FS-lite: to support PE
→ Task #7228: FS-lite: to support Olympus
→ Task #7229: FS-lite: to support Olympus
→ Task #7234: FS-lite: to support Gatan
→ Task #7230: FS-lite: to support AP
The formats have been tested.

@ximenesuk
Copy link
Contributor Author

The delete functionality added in 19c936e is fairly simple and designed to delete a file set immediately following an upload before any changes have been made to the db. However, this still raises some questions:

  • should files actually be deleted or moved to some hidden trash area? (Maybe an import/upload can be resumed later?)
  • should deletes be honoured if there is some db reference to a file?

@ximenesuk
Copy link
Contributor Author

Closing this PR as the work really needs to be rebased on develop as due to the chgrp work there are too many conflicts with Insight code.

@ximenesuk ximenesuk closed this Mar 22, 2012
chris-allan added a commit to chris-allan/openmicroscopy that referenced this pull request Sep 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants