Discussion: Info popups

[kintopp]

The sample data will need to be provided per element.. that is, separate info texts for each functional area in the detail view.

[kintopp]

At present I see this as an e.g. 1-2 paragraph length text field which can be used to describe the functionality of the respective element. It should be able to render basic HTML elements so that we can include images, tables, formatted lists and similar. I'd like to confer with Miranda on this as well.

[kintopp]

@gklyne Could you please point me to (or create a new slot for, in the Opele sample RDF) where I should add the help/descriptive text for the 'Info' popups associated with elements of the place record detail view? See comment above on anticipated content. We'll need these for:

• Preferred name/toponyms (one entry for both)
• Current administrative hierarchy
• Location
• Citation
• Permanent URL
• Name Attestations
• Calendars
• Related Places
• Related Resources
• Bibliography
• Export
• Maps
• Description
• Historical Hierarchies

For now, please just use some 'lorem ipsum' placeholder text for all elements:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

[gklyne]

I'm not sure about the requirement here.

Specifically, is the "info" pop-up text specific to a place, or is it about the field more generally? Also, is there any common content across all the above examples? (Sorry if we already discussed this, but I've rather lost context on this atm.)

[kintopp]

It is hard to keep it all straight (and I'm forgetting things too). The Info field is used to describe an element or feature generally, and so is defined once. Thus, it shouldn't really be part of the Opele sample RDF but be stored in Timbuctoo. But at present, we have no other place to put this. I'll raise this with @marnixvb tomorrow.

[gklyne]

OK, I thought possibly this was the case. I haven't yet given consideration to this aspect of the data.

It could be (and maybe should be) in the data we provide, but just once. Like the Opole sample data file up to about line 285. As such, it could be a single Turtle file (eventually) separate from the GeoNames and other place data. It should probably be part of or linked from some kind of schema file for the EMPlaces data. E.g., text attached to the property and/or class URIs.

As for rendering basic HTML elements, I use Markdown quite a lot in my Annalist data collections.

Something to discuss with @marnixvb is the possibility of providing some rendering hint with the data... though on reflection I suspect this would be in the Timbuctoo configuration (which, as I understand it, is initially auto-generated, but can then be adjusted by hand to get a more pleasing display).