https://github.com/ome/ome-mdbtools
Java API to handle Microsoft MDB format (Access). Used by Bio-Formats for Zeiss LSM metadata in MDB files.
https://github.com/ome/ome-mdbtools
mdb
Last synced: 11 months ago
JSON representation
Java API to handle Microsoft MDB format (Access). Used by Bio-Formats for Zeiss LSM metadata in MDB files.
- Host: GitHub
- URL: https://github.com/ome/ome-mdbtools
- Owner: ome
- License: lgpl-2.1
- Created: 2016-10-20T21:26:07.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2024-04-16T11:19:18.000Z (about 2 years ago)
- Last Synced: 2025-06-14T03:38:30.086Z (12 months ago)
- Topics: mdb
- Language: Java
- Size: 426 KB
- Stars: 4
- Watchers: 6
- Forks: 10
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# OME MDB Tools
[](https://github.com/ome/ome-mdbtools/actions)
[](http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.openmicroscopy%22%20AND%20a%3A%22ome-mdbtools%22)
[](http://javadoc.io/doc/org.openmicroscopy/ome-mdbtools)
This is a fork of the [mdbtools-java](http://mdbtools.cvs.sourceforge.net/viewvc/mdbtools/mdbtools-java/) project. There are numerous bug fixes, as well as changes to reduce the memory required for large files. There are no dependencies on other components.
More information
----------------
For more information, see the [MDB Tools project on GitHub](https://github.com/mdbtools/mdbtools).
Pull request testing
--------------------
We welcome pull requests from anyone, but ask that you please verify the
following before submitting a pull request:
* verify that the branch merges cleanly into ```master```
* verify that the branch compiles using Maven
* verify that the branch does not use syntax or API specific to Java 1.8+
* make sure that your commits contain the correct authorship information and,
if necessary, a signed-off-by line
* make sure that the commit messages or pull request comment contains
sufficient information for the reviewer(s) to understand what problem was
fixed and how to test it