Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions to improve search node events page #78

Open
cyprien-griot opened this issue Jan 20, 2021 · 3 comments
Open

Suggestions to improve search node events page #78

cyprien-griot opened this issue Jan 20, 2021 · 3 comments

Comments

@cyprien-griot
Copy link
Collaborator

Greetings all,

After a few experiments, we noticed it could be interesting to have the possibility of :

  • sorting search results according to columns
  • exporting results into a csv file (or something similar)

Thank you in advance.
Regards,
Cyprien

@cyprien-griot
Copy link
Collaborator Author

Greetings,

This features request has popped up again within our team.
Is this something that could be doable ?

Thanks in advance.

Regards,
Cyprien

@beaudu
Copy link
Member

beaudu commented Jun 20, 2022

In the release v2.5 the CSV export is now available. For the search result sorting by columns, it is still to be done.

beaudu referenced this issue Jun 20, 2022
    - grids column is now optional (checkbox) and desactivated by default,
    - full node name can be displayed (checkbox),
    - a link allows to download a .csv file of the results,
    - a wait icon appears during the search.
@beaudu
Copy link
Member

beaudu commented Jun 20, 2022

Some comments on the future development. Presently the strategie of vsearch.pl script is:

  1. events are selected from the criteria with searchEvents() sub (lines 479-555) that uses external commands (find, grep, awk, ...) and returns the list of event filenames in array @finalEvents;
  2. the filenames contain node ID and start date/time of the event, so it is possible to sort by date or revert date at that point (see lines 200 and 201).
  3. in a loop, events are read and decoded one by one and displayed as a html table.

So in order to sort events on other criteria (node alias, feature, author, etc...), events must be read and decoded first and stored in some array or hash, then sorted, then displayed in a different loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants