Task #10993 (closed)
Opened 11 years ago
Closed 11 years ago
Fake companion files
Reported by: | jamoore | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 5.0.0-beta1 |
Component: | General | Version: | 4.4.8 |
Keywords: | n.a. | Cc: | omero-team@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
It should be possible for a fake file to specify that another file is to be used as a companion file. This could either be hard-coded in the reader:
$ touch foo.fake $ touch.foo.fake.companion
or a more extensible mechanism of specifying the the entire used files array could be used:
$ touch foo.fake # This will be the first element of usedFiles $ echo "usedFile&companion=true:foo.fake.log" >> foo.fake $ echo "usedFile&series=1:foo.fake_1" >> foo.fake
The more extensible version should only be approached after looking at all of the new features in this story. Decisions must be made on the internal format of fake files if we are to do this: Java properties files? INI files? "foo&contents=ini.fake" ?
Change History (2)
comment:1 Changed 11 years ago by jamoore
- Priority changed from minor to major
comment:2 Changed 11 years ago by mlinkert
- Resolution set to fixed
- Status changed from new to closed
- Version set to 4.4.8
Closing, as PR 536 above was merged. The companion file for 'foo.fake' would be 'foo.fake.ini', and can contain INI properties.
PR added to support ".fake.properties" files : https://github.com/openmicroscopy/bioformats/pull/536/files
Leaving this open for the moment, since this is just one suggested solution for the problem.