Changeset 35066


Ignore:
Timestamp:
2021-04-12T22:42:45+12:00 (3 years ago)
Author:
davidb
Message:

Text/syntax tidy-up

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/trunk/model-sites-dev/eurovision-lod/collect/eurovision/transform/pages/about.xsl

    r35061 r35066  
    195195         WHERE {
    196196           GRAPH &lt;<xsl:value-of select="$graphURI"/>&gt;  {
    197                        ?s gsdlextracted:Country ?country
    198            }
     197               {
     198             SELECT DISTINCT ?country ?year WHERE {
     199                 ?s gsdlextracted:Country ?country.
     200                 ?s gsdlextracted:Year ?year.
     201             } ORDER BY ?country ?year
     202               }
     203             }
    199204         }
    200          GROUP BY ?country ORDER BY asc(?country)         
     205         GROUP BY ?country ORDER BY ASC(?country)
    201206           </xsl:attribute>
    202207           <xsl:text> Loading ...</xsl:text>
     
    245250        </li>
    246251          </ul>
    247         you will find a set of samples you can test-drive to give you an idea of the
    248         sorts of raw data analysis that can be done.  The syntax used is called
    249         <a href="https://en.wikipedia.org/wiki/SPARQL" target="_blank">SPARQL</a> (pronounced &quot;sparkle&quot;).  If you are unfamiliar
    250         with this syntax, there are a variety of tutorials available online where you can learn about query language, such as
    251         the one done by <a href="https://jena.apache.org/tutorials/sparql.html" target="_blank">Apache Jena</a>, an Open Source
    252         initiative that provides a variety of Semantic Web and Linked Data tools.
    253         As before, these samples are editable so you are free to
    254         change them however you wish to adjust the analysis undertaken, or once you're mastered the
    255         query syntax, develop completely original forms of
    256         analysis.
    257       </p>
    258 
    259        
    260         <p>
    261           We suggest starting with viewing <a href="{$library_name}/collection/{$collName}/page/sgvizler">sample visualizations</a> to see what's possible,
    262           and making minor edits to that to adjust what is visualized.
    263           Then, if you want to start visualizing the data in a more substantially different way
    264           or else export the data for more detailed analysis under your own control,
    265           switch to the <a href="{$library_name}/collection/{$collName}/page/sparql">SPARQL-based data analysis</a> page to ensure the underlying
    266           data retrieved is as you intended.  Then take the newly developed SPARQL query back to the visualizer page, and through the
    267           additional text-input fields provided there, develop the visualization.
    268 
    269           <!--
    270         This is a good place to go to see what sort of data is being stored, and we provide some sample
    271         queries to get you going.  But if you like to see the data presented more visually, we suggest
    272         you try out the
    273 
    274         <li><a href="{$library_name}/collection/{$collName}/page/sgvizler">SGVizler page</a></li>
    275 -->
    276         </p>
     252          you will find a set of samples you can test-drive to give you an idea of the
     253          sorts of raw data analysis that can be done.  The syntax used is called
     254          <a href="https://en.wikipedia.org/wiki/SPARQL" target="_blank">SPARQL</a> (pronounced &quot;sparkle&quot;).  If you are unfamiliar
     255          with this syntax, there are a variety of tutorials available online where you can learn about query language, such as
     256          the one done by <a href="https://jena.apache.org/tutorials/sparql.html" target="_blank">Apache Jena</a>, an Open Source
     257          initiative that provides a variety of Semantic Web and Linked Data tools.
     258          As before, these samples are editable so you are free to
     259          change them however you wish to adjust the analysis undertaken, or once you're mastered the
     260          query syntax, develop completely original forms of
     261          analysis.
     262      </p>
     263
     264     
     265      <p>
     266        We suggest starting with viewing <a href="{$library_name}/collection/{$collName}/page/sgvizler">sample visualizations</a> to see what's possible,
     267        and making minor edits to that to adjust what is visualized.
     268        Then, if you want to start visualizing the data in a more substantially different way
     269        or else export the data for more detailed analysis under your own control,
     270        switch to the <a href="{$library_name}/collection/{$collName}/page/sparql">SPARQL-based data analysis</a> page to ensure the underlying
     271        data retrieved is as you intended.  Then take the newly developed SPARQL query back to the visualizer page, and through the
     272        additional text-input fields provided there, develop the visualization.
     273
     274      </p>
    277275
    278276      </div>
     
    285283          });
    286284      </gsf:script>
    287 
    288285
    289286<!--
     
    298295      </p>
    299296
    300 -->
    301 
    302 
    303 <!--     
    304       <div style="padding-top: 6px;">
    305         So the above visualization show how many times each country has entered, over the years, but what about how
    306         many times countries have won?  And what about how many times countries have won per head of population?
    307         <ul>
    308           <li>
    309         <a href="{$library_name}/collection/{$collName}/page/sgvizler"><i>Show me more visualizations ...</i></a>
    310           </li>
    311         </ul>
    312       </div>
    313297-->
    314298
     
    346330      </p>
    347331     
    348       <!--
    349           The resulting SPARQL query result set (JSON format
    350         selected for output) is then ingested into a Greenstone
    351         DL collection, and used in a variety of ways.
    352 
    353        
    354 
    355         the starting point is the
    356         formulation of a SPARQL query to retrieve from DBpedia
    357         entries about all the entrants in the contest over the
    358         years:
    359       -->
    360 
    361332
    362333      <div id="dl-tech-show-more">
     
    374345          returned to be prior to 2020.
    375346        </p>
    376        
     347<!--
     348#    bind( REPLACE(str(?country_in_year), ".*(\\d{4})", "$1") AS ?year).
     349
     350PREFIX rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;
     351xsd:
     352skos:
     353prov:
     354
     355dbc:
     356dbp:
     357
     358dct:
     359-->     
    377360        <pre style="background-color: #fff; color: #000; padding: 12px; margin-right: 6px;">
    378361SELECT ?countries_in_esc_by_year ?country_in_year (?year AS ?Year) (?country AS ?Country) ?entrant (?entrant_label AS ?Creator) ?song (?song_label AS ?Title) (?was_derived_from AS ?WikipediaURL)
     
    381364
    382365    ?country_in_year dct:subject ?countries_in_esc_by_year.
    383 #    bind( REPLACE(str(?country_in_year), ".*(\\d{4})", "$1") AS ?year).
    384366    ?country_in_year dbp:year ?year.
    385367    FILTER ( xsd:integer(?year) &lt; 2020).
Note: See TracChangeset for help on using the changeset viewer.