Replace strings like Custom5, Custom3 with NAs

[lucalamoni]

This is one of the points we discussed at the meeting on the 24th of October.

Sometimes empty custom ref points and empty custom data columns in SAG have strings like Custom3, Custom5 etcc. Would it be possible to substitute these values with NAs?

[cmspinto]

Does this issue occur during the download process, within the web services, or in both?

From what I can see, it seems the submitter did include those values. I don’t believe there’s any risk in removing them from the database, as we can always verify if there are values associated with those headings. However, could you clarify why it is important to remove these custom names?

[lucalamoni]

both @Milldaz and me noticed this mostly in custom ref points names, here is an example below:


https://standardgraphs.ices.dk/ViewSourceData.aspx?key=18508
These custom ref point names don't seem to correspond to any value. Maybe there is a reason for this that I am not aware of.

[Milldaz]

Yes, this is a template error (the template has these names pre-filled). I think we should scan through the database and delete all Custom Ref Pts with those names and no value associated with it.

[cmspinto]

Hi, I have done a query in the database and there are 5 stocks where this happened, here is the list of the of the stocks where this happened:

This needs to be researched in the next meeting, because they actually have values these series:

So we can't just delete these data, we need to go one by one of these 5 stocks to check if this information is important.

[cmspinto]

For these two stocks there was name of the columns but no values in the custom columns: 10284, 10309

So these two were updated but it's possible to revert the changes.

[Milldaz]

We were talking about CustomRefPointName (the reference points), not CustomName (the time series).

[cmspinto]

I checked both ;), but the issue is also about the data values, this is the text:

About the customRefName we need to check it in the next meeting:

[lucalamoni]

It might be that I made an error in my description and as @Milldaz said, this issue is localised to the CustomRefPointNames in the template.