We have some relics of earlier processing or plans in our codebase which (we believe) can be removed without fallout:
We pointlessly construct an @id attribute for HTML documents which don't have one during the tokenize stage. For the purposes of document identity, we use the URI relative to the search page, but at some stage we presumably used or considered using the @id attribute on the <html> element, and we therefore construct one if there isn't one. That code can go (it's in the template matching html in the clean mode).
We pointlessly output that docId into the JSON stem files, which makes them slightly bigger. That can go from the makeMap template.
We have a method of the StaticSearch object called StaticSearch~getDocIdsForFilters(), but it's not using document ids; it's using the docUri relative paths that we adopted as identifiers. It should be renamed to avoid confusion to StaticSearch~getDocUrisForFilters().
We have some relics of earlier processing or plans in our codebase which (we believe) can be removed without fallout:
We pointlessly construct an
@id
attribute for HTML documents which don't have one during the tokenize stage. For the purposes of document identity, we use the URI relative to the search page, but at some stage we presumably used or considered using the@id
attribute on the<html>
element, and we therefore construct one if there isn't one. That code can go (it's in the template matching html in the clean mode).We pointlessly output that docId into the JSON stem files, which makes them slightly bigger. That can go from the makeMap template.
We have a method of the StaticSearch object called
StaticSearch~getDocIdsForFilters()
, but it's not using document ids; it's using the docUri relative paths that we adopted as identifiers. It should be renamed to avoid confusion toStaticSearch~getDocUrisForFilters()
.