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

Provide direct file system access to the Mission and Expedition figures directories #78

Open
MBARIMike opened this issue Sep 30, 2021 · 6 comments
Labels
original use case Translated from Use Case document

Comments

@MBARIMike
Copy link
Contributor

From the Use Case document:

View the path to the mission directory, or the expedition’s Figures directory, or the current working directory. Click to open a Finder window or terminal window to that directory (or if that’s not recommended, just allow the path to be copied).

@MBARIMike MBARIMike added the original use case Translated from Use Case document label Sep 30, 2021
@jbpaduan
Copy link
Collaborator

jbpaduan commented Dec 2, 2021

The table "Compilation" was originally conceived to be useful for this purpose. It will be especially useful for providing someone with the definitive map for a mapped area, and finding where the most current figures and navadjust project are; these will change with time as more missions are added, and we will need some way to update them. But with Dave's interest in being able to search for projects in which a mission is part, and conversely, the see the missions that were part of a project, it seems that what is needed (instead of or in addition to Compilation) is a list associated with each mission of all directories/paths that have a datalist or datalists with that mission in it.

@MBARIMike
Copy link
Contributor Author

MBARIMike commented Dec 2, 2021

Should the Compilation table have a many-to-many relationship with the Mission table?
(Related to #80 (comment))

@jbpaduan
Copy link
Collaborator

jbpaduan commented Dec 2, 2021

I lean that way, then recoil. There has to be just one place where the latest-latest navadjustment was made, which generated the .na0 ancillary files in that mission. We need to keep track of that. (I'm thinking that should be something Dave captures in the .par files.) I was hoping we could coalesce on making it a practice of having a single place, updating to a new year/directory as needed, where the latest-latest map is that uses a mission. At the moment we aren't so disciplined, and part of it is that there are multiple projects that may utilize a mission, as Dave indicated.

@MBARIMike
Copy link
Contributor Author

MBARIMike commented Dec 2, 2021

It would be straight forward to write a program to walk all the datalist*.mb-1 files and create Compilation records with relationships to Missions. We can then have some sort of mechanism to identify where the latest-latest navadjustment was made.

@MBARIMike
Copy link
Contributor Author

Regarding:

Click to open a Finder window or terminal window to that directory (or if that’s not recommended, just allow the path to be copied).

The name field for Mission and Compilation is populated with the directory name and is displayed at the top of the detail web pages. It can be copied and pasted into a terminal window.

@jbpaduan
Copy link
Collaborator

This issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
original use case Translated from Use Case document
Projects
None yet
Development

No branches or pull requests

2 participants