UWLSWD index page

[cspayne]

remaining to-dos

• [x] @briesenberg07 complete shared-email setup for uwlsemanticweb@uw.edu
• [ ] Add uwlsemanticweb@uw.edu as contact for index (also need separate issue(s) to add contact info as part of main.py workflow)
• [x] Confirm all resources have schema:disambiguatingDescription
• [ ] Replace uwlswd/xsl/temp_index.xsl with index.xsl*, which:
  • [ ] Sorts resources using schema:disambiguatingDescription values
  • [ ] Fetches @en human-readable information (titles, descriptions, disambiguatingDescriptions, etc.) for index

* to-be-written

Summary

Output/update comprehensive HTML index page at UWLSWD repository each time a dataset is added/updated, perhaps with additional details for each resource. Eliminate multiple links to datasets/vocabs from University of Washington Libraries Semantic Web Resources, simply link to this index.

[briesenberg07]

@cspayne thank you for sharing the draft index page**! This is a great starting point. \I'd like to improve the presentation with some sorting, and perhaps in future, present the resources in categories.

• Sorting: xsl:sort could be implemented to sort alphabetically by titles/title, or in some other useful way
• Categorization: This is probably for the future. I don't imagine that our current DataCite XML provides any values which could be used to divide resources into categories... but this might be possible in future. Specifically, we've talked about coming up with meaningful but brief phrases for resourceType...

<?xml version="1.0" encoding="UTF-8"?>
<resource>
   ...
   <resourceType resourceTypeGeneral="Dataset">brief phrase here</resourceType>
   ...
</resource>

...perhaps these could be used to sort into categories? Or, if we add other elements to our DataCite descriptions, something else??

** Draft .html published! https://uwlib-cams.github.io/uwlswd/

[briesenberg07]

One other point of feedback, and I'm not sure what to do here--

It's a big overwhelming list! This isn't any shortcoming in Cypress' work, it's just that we've published a lot of resources, which constitute a long list with lots of titles and lots of text, and that's all there is to it!

But, is there any way to make these more digestible? Brainstorming:

• A search box at the top of the page above the list would help, but I don't think you can do that with a static page (can you?)
• What about presenting a simple list at top, and a full listing with details at bottom? Something like**:

• Instances of the aggregation class [[go to this resource on the web]()] [[go to details below]()]
• Linked Data Platform Vocabulary [[go to this resource on the web]()] [[go to details below]()]

[...then, below...]

[Instances of the Aggregation Class]() Instances of the class represented in the University of Washington digital collections; the class is taken from the Digital Public Library of America Metadata Application Profile 5.0 [Linked Data Platform Vocabulary]() RDFS vocabulary establishing classes and properties needed to describe platforms used to process RDF datasets. The word platforms represents applications, software, scripts, programs, etc. useful in processing the datasets. [...]

• Or, a table, with titles in a left-hand column and descriptions in a right-hand column?
• Or, something else??

** Note that these links don't go anywhere

[briesenberg07]

Continuing to brainstorm options for making a less-listy page which (I think) could be accomplished in a static page:

• Navigation pane with (short-)title-only links to full descriptions at left- or right-hand side?
• ...

[cspayne]

see recent commit: update index to include resourceType

[briesenberg07]

A ~couple of~ few additional index to-dos:

• [x] Get "Instances of the ProvenanceStatement Class" into the correct category [1A] -- @briesenberg07 will do this as the error is probably in temp_index_categories.xml
• [x] Update index_pages.css so that all description text has a left margin [1B] -- @cspayne changing indent-text to margin-left in index_pages.css [2] seems to do what I want but I'm not sure whether this might cause problems for any other index pages. OK to make this change?
• [x] Add backlink from index to University of Washington Libraries Semantic Web Resources
• [ ] Add email contact to index - @briesenberg07 will do this once shared-email setup for uwlsemanticweb@uw.edu is complete

[1A+B]

[2]

[cspayne]

• [ ] Update index_pages.css so that all description text has a left margin [1B] -- @cspayne changing indent-text to margin-left in index_pages.css [2] seems to do what I want but I'm not sure whether this might cause problems for any other index pages. OK to make this change?

Not a problem! The UWLSWD index page is the only page using the indent class.

[cspayne]

@briesenberg07 Is this issue ready to be worked on? I'm happy to take it on if so.

[briesenberg07]

Thank you @cspayne -- looks like 2 out of 3 of the still-to-do tasks above could be worked on right away:

1. 👎🏻 Add email contact to index - this can't be done yet, once @gerontakos makes me owner of the shared NetID uwlsemanticweb I can get email set up for the ID and we can begin plastering it all over UWLSWD
2. 👍🏻 Replace any lang tags which are not IETF Best Current Practice 47 (IETF-BCP47) language tags - can't quite remember why this was an index issue... I think there are a couple of lang-tag issues in UWLSWD_cleanup, and checking for non-BCP-47 tags is in the checklist, but I'm not sure why it'd be an index issue (index page has no RDFa, thus no embedded lang tags...). So I don't think it's an index issue, but I do think there are more lang tags out there that need cleaning up and this can be worked on.
3. 👍🏻 Replace uwlswd/xsl/temp_index.xsl with index.xsl - if the remaining needed schema:disambiguating description values can be added, then I believe we can implement a new style sheet for generating the index. So it'd be a multi-step process, but this can be worked on. If you get into writing the new stylesheet, note that I demoted the VoID description to the lowest slot in the index TOC.