Task #11636 (new)
Opened 11 years ago
Last modified 9 years ago
API for file path sanitization
| Reported by: | mtbcarroll | Owned by: | mtbcarroll |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | OmeroFs | Version: | n.a. |
| Keywords: | n.a. | Cc: | fs@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Since https://github.com/openmicroscopy/openmicroscopy/pull/1109 the rules for how file paths must be sanitized for import are a server configuration option. However, ImportLibrary.createImport just guesses at what the server will accept.
One could add a server API method that actually tells what the rules are, and then the client could query and apply them in creating the proposed FilesetEntrys, thus sanitizing exactly as much as necessary for the current setting of omero.fs.repo.path_rules.
(Or, if preferred, the client could attempt without sanitization, and use the detail of the resulting FilePathNamingException from importFileset to fix accordingly in iterative attempts.)
Change History (2)
comment:1 Changed 10 years ago by mtbcarroll
comment:2 Changed 9 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Further, a String → String API method could be offered that does sanitization according to the current server configuration, allowing clients to easily offer some kind of interactive management of adjustments to paths.