Support photo musea on the maps

[vdhamer]

Rationale

Because we already show each photo club on a map, it is not an enormous step to also show photo musea on the map.

Benefits:

1. The target audience for the app occasionally visits photo musea in their area or when traveling..
2. Map locations are more relevant for musea than for photo clubs: musea are open most of the time, but photo clubs aren’t.
3. Museum information is available in the public domain (e.g. on Wikipedia)
4. World-wide musea locations conveys that the app is not necessarily Netherlands-only.
5. The feature allows for cool 3D map screenshots for the App Store. Musea are partly in big cities (Tokyo, New York, Berlin) and may have nearby tall or interesting buildings.

Drawbacks:

1. It's arguably feature creep.
2. Loading the extra JSON data costs max 1 kB extra per museum. The data loading happens in the background.
3. User may not immediately notice the feature. But that is ok.

Data Model

Museum records will be stored in the PhotoClubs table and may be renamed to the Organizations table at some point.

• Use a relation to an extra LocationType table containing the allowed values.
  The LocationType table controls the possible values of PhotoClub.LocationType and allows additional values in the future (the B&H Superstore in Manhattan, locations of manufacturers’ headquarters) without adding additional booleans. But these extensions seem contrived.

The JSON input file format for this is discussed in the Architecture chapter of README.md. An example file can be found as ClubList.json.

Photo Club screen - 1st release: show musea on maps

INITIALLY show only sections representing Photo Clubs (with musea markers if they are in the displayed region).

• the page title stays becomes "Clubs" to save space (for a future toggle)
• load both lists ("clubs" and "museums") from the ClubList.json file
• this means the outer query should filter on isMuseum to find the photo clubs only for generating sections In contrast, the inner query should not filter on isMuseum, and just show all records for displaying markers. On any map you could see all 125 items if you zoom and pan far enough.
• Musea are represented on the maps using a dedicated blue marker (temple/museum symbol in SF)
• Test on first install.
• Test on upgrade install. Likely to give issues.
• update in-app Readme screen
• update README.md text

Photo Club screen - 2nd release: new search bar on Clubs screen

• The search bar would filter the displayed sections=Clubs using their full name, or possibly town and country. Note that the displayed town/country are localised. "London" won't match "Londen" and vice versa, but both will match "Lond".
• update in-app Readme screen
• update README.md text

Photo Club screen - 3rd release: mode for Clubs vs Musea

LATER add a toggle (aka SwiftUI Picker) between focussing on Clubs or Musea. Assume there are 100 clubs and 25 musea.

• when the museum corresponds to a section, the museum marker is purple instead of blue
• A mode toggle would either show 100 Photo Club sections (=maps) or 25 Musea sections (=maps). But on any map in either toggle state you could see all 125 items if you zoom and pan enough. No toggle possible to hide musea altogether (possible, but adds complexity to user).
• The search bar behavior and prompt would toggle between finding Clubs or Musea .
• the page title is "Clubs" or "Musea" - depending on the toggle state (complicating the readme: Locations or Maps?).
• update in-app Readme screen
• update README.md text

Portfolios screen

• no changes. Only shows hierarchy Clubs/Photographers/Images.
• for now the photographers have no direct relationship to photo musea (hope it stays that way)

Preferences screen

• no changes. But needs refactoring because it only impacts Portfolios page. Title change?

Readme screen

See text updates above.

Who's Who screen

• no changes. Only shows hierarchy Photographer/Clubs/Images
• for now the photographers have no direct relationship to photo musea