Improve and standardize the Dates folder in all the Primo Subject Areas
The following are available in the Dates folder for Primo Action Usage, Primo Device Usage, Primo Facet Usage, Primo Sessions, Primo Zero Search Results and Primo Pipes:
Year (date)
Year
Year (desc)
** all three are the same format: YYYY
** why are there three?
Month (date)
Month (short desc)
** these two are the same format: Mon YYYY
** why are there two?
** shouldn't "Month (date)" really be Month (as in January, February, March, etc)?
Month (long desc)
** uses the Month YYYY format.
** why?
Month (number)
** displays as expected
Week (date)
** uses Mon DD
Week (short desc)
** uses Mon DD
Week (long desc)
** uses Mon DD, YYYY format
Date
** uses Mon DD format
** shouldn't this be MM DD YYYY?
Date (short desc)
** uses Day, Mon DD format
Date (long desc)
** uses Day, Mon DD, YYYY format
DOW (number)
** displays as expected
The fields aren't labeled very clearly. There's no documentation (as of the writing of this idea) explaining any of the fields in the OLH. There are duplicates without any explanations as to why.
A field for just Month is missing.
A field for just the date is missing. At a minimum, the full date should be one of the fields so that users can create their own date calculations (like day of the week without Mon DD or Month with YYYY)
A "data updated as of" field is missing.
The fields aren't consistent across all of the Primo Subject areas:
-- Primo Popular Searches has seven fields (where Month (long desc) has already been reported as a bug as of the writing of this idea).
-- Primo PNX Records has eleven fields.
Lesli M Moore
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 30 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Primo.
Best regards,
Primo Product Team