sapa / performing-arts-ch-templates

1 stars 3 forks source link

ArchivPlan -> delete sub-section (bug) #368

Closed b2d3c closed 1 year ago

b2d3c commented 1 year ago

Apparently, after #186, the sub-section to delete are always here.

image

Could you delete them?

Thanks !

fkraeutli commented 1 year ago

Sorry, just to refresh my brain. I think what we did in #186 is to only mark them for deletion. Should we now delete them (i.e. their named graphs)?

The subsections marked to delete are:

PREFIX crm: <http://www.cidoc-crm.org/cidoc-crm/>
SELECT * WHERE {
  ?subsection crm:P3_has_note "markForDeletion" .
}
b2d3c commented 1 year ago

I have control they are not linked with entities uo and down.

PREFIX rico: https://www.ica.org/standards/RiC/ontology# PREFIX crm: http://www.cidoc-crm.org/cidoc-crm/ SELECT * WHERE { ?subsection crm:P3_has_note "markForDeletion". OPTIONAL {?subsection rico:isOrWasIncludedIn ?sursection}. OPTIONAL {?sousection rico:isOrWasIncludedIn ?subsection} }

It's no more the case. You can also delete them now. Thanks.

fkraeutli commented 1 year ago

Check content

SELECT DISTINCT ?subsection (COUNT(?s) as ?num_statements) WHERE {
  GRAPH ?g {
    ?subsection crm:P3_has_note "markForDeletion" .
    ?s ?p ?o .
  }
} GROUP BY ?subsection
ORDER BY DESC(?num_statements)
fkraeutli commented 1 year ago

Delete query:

DELETE { 
  GRAPH ?g {
        ?s ?p ?o
  }
} WHERE {
  GRAPH ?g {
    ?subsection crm:P3_has_note "markForDeletion" .
    ?s ?p ?o .
  }
}

Executed on dev. @b2d3c Can you check the result on dev before I execute it on prod?

b2d3c commented 1 year ago

It's fine. You can deployed in prod. Thanks!

fkraeutli commented 1 year ago

deployed