Closed rushirajnenuji closed 4 years ago
Ah, good catch
Hi @laurenwalker - the way we’ve done this for a DC view is to set a filter object to exclude these formatIds
on the searchModel
. But for the /profile
view, we do not have a searchModel
, we directly generate queries in StatsModel. So, I’ve appended these filters to those queries. I’ve verified the numbers and they look okay, but I was wondering if this approach sounds correct.
It would be great if you could review the following commit. Thanks! https://github.com/NCEAS/metacatui/commit/fb2e3809acace551dfdd4474844219f00f4af266
Nice catch and debugging, @rushirajnenuji. I'm not overly-familiar with how we're exposing portals to users but I'm wondering if we may also want to set up our Solr instances to hide Portal objects by default from all searches so explicit filtering isn't necessary?
Hey @amoeba - thank you for taking a look at this. Interesting to know that we can hide a specific type of object from searches. We might have more than one use case, but one I can think of is the collectionQuery
attribute that @gothub got indexed within solr
for Portal objects. Both our DataONE services depend on this query attribute to generate aggregated metrics.
@rushirajnenuji - That commit looks good to me. Thanks!
Thank you, Lauren. I'm closing this issue.
If we visit
https://arcticdata.io/catalog
- we get the DataCatalog page which displays the total count of publicly available datasets. Right now the view shows5787
total datasets. If we visit thesummary
viewhttps://arcticdata.io/catalog/profile
we have5790
total datasets. After inspecting thesolr
queries, the difference in the totals seems to be from the three additionalportal
objects that we have onurn:node:arctic
. The same thing applies tourn:node:KNB
.We can solve this easily by updating the queries for
/sumary
view to eliminate portal objects from the total counts.