Closed ColmMassey closed 4 years ago
and 2. seem to be both defined in the about.html
page already, correct?
And 3. are listed in the database page already, correct?
Tentatively implemented a configurable option showDatasetsPanel
on the branch dot-coop-coops-uk-merge
.
We have a pretty good idea of what is needed. Will be discussed with Nick and Colm today to make sure we understand the task.
to solve 1 and 2 we just need a write up for the about section for the dotcoop/coops-uk2019 merger
That's an action for Colm (supply the text for the about page etc.).
Given that, I think I understand what to do, but will make a sketch just to confirm.
If I'm right this should clarify?
Point 1 and 2:
Point 3
The final point is just to make the datasets tab optional, by a parameter in config.json
Can you point to the place in the repository where the About html is put for the current Oxford and DotCoop maps?
What else should we put in the About? A version #?
Can you point to the place in the repository where the About html is put for the current Oxford and DotCoop maps?
This, for example, defines what goes into the about tab for the coops UK 2017 "variant" of the map-app. Each variant can have its own.
The about is fairly free-form. But we could pull in the version from the version.json file which is generated when the map-app site is built.
@ColmMassey - is this ticket still a priority for Code Operative Org Sprint 2? Or should we down-prioritise it?
Yes, let's leave this until next month.
I'm splitting this issue into
We can postpone working on 2 until we are finalising a multi graph map implementation.
We now have a 'selected database' view in the panel, to support selection when more then one linked data graph is being used to populate the directory/map.
We have the following type of info to be displayed somewhere.
Let's keep 1 and 2 in the i/About panel, and have 3 in the database page.
Let's have an option on the configuration file to disable the database panel altogether. The reason for this is that in the past, we often had requests to keep the interface as clean and untechnical as possible, for some audiences.