Donate | Contact | Search

Usage tips / possible problems & solutions

• To restart navigation from the top, repeatedly tap (or just hold down) the ESC key until the screen stops changing.
• If in doubt read the screen. If still in doubt, reread it, more slowly and carefully. If still in doubt, see the mailing lists.
• OM seems easier to use if you first learn the keystrokes for copy/paste in the terminal (command) window you are using (or assign them, as needed).
• Ideas for organizing information
• Maybe OM should automatically provide various entities as attribute types (paragraph, quote, length, weight, kilometers, & relation types). Worth discussing.
• It is VERY IMPORTANT to do PostgreSQL backups, so you don't lose your data, or so you can go back to an earlier point in time if ever necessary.
• It is easiest to do some operations w/ multiple tabs or windows open. For example, if you find info you want to move an entry from one distant group to another:
• There is no "save" operation: it is continual. Killing open instances of OneModel (ie, the java process) does no harm, as far as I can imagine or have seen.
• Importing data to include text attributes (eg paragraphs, any content that *must* be 160 characters per line):
• Let's judiciously share what we learn, that might help others.
• If you get an error including this near the end: "Caused by: org.postgresql.util.PSQLException: FATAL: terminating connection due to administrator command"
• FileAttribute sizes: I read that the Postgres "large object facility...allows values up to 4 TB in size", but I have not tried anything even near a gigabyte.
• (continue here)=========================== [This is here as a tip: sometimes I use an entry like this in a list, for a visual separation.]
• About relationships: the system creates "has" by default, which helps, and there might be more we want to auto-create or standardize. Here are others I use:
• 
• ...(in the 2nd half of the image). However, for bi-directional relation types, only one direction is shown.
• If you get a bug that seems to lock you in to a screen and you can't get out, just ^C (Ctrl+C) and restart OM.
• About line editing AND SEARCHING (notes, probably still accurate as of 2016-01-21)
• OM seems much easier to use if you first configure your terminal or command window to enable scrolling backward to see previous work, when needed.