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

Sort transactions for any activity #379

Closed
stevieflow opened this issue May 19, 2017 · 9 comments
Closed

Sort transactions for any activity #379

stevieflow opened this issue May 19, 2017 · 9 comments
Labels
Projects

Comments

@stevieflow
Copy link

As someone who uses d-portal to look at individual actitivities, I would like the function to be able to sort any of the columns within the transaction table (A-Z , Z-A) in order then by date, type, provider, receiver or value. I would specifically like to do this so I can see all Incoming Funds together in one grouping, for example

@notshi notshi added the feature label May 19, 2017
@notshi notshi added this to Other TO DO in SAVi Sep 21, 2017
@stevieflow
Copy link
Author

bump.... !

@stevieflow
Copy link
Author

The more I use d-portal, the more useful this would be

@stevieflow
Copy link
Author

I'd really like to see this function!

@notshi
Copy link
Collaborator

notshi commented Jan 5, 2019

Thanks, @stevieflow - this might take some time but for the moment, transactions are now grouped by type.

Example - http://d-portal.org/ctrack.html#view=act&aid=NL-KVK-40594571-WAI2016

@stevieflow
Copy link
Author

Thanks @notshi - interesting

( I suspect some users will also value the chronological list of all transactions - it's a tricky one)

In terms of Incoming Commitments then I'd suggest to position them above the Incoming Funds, in this view. This makes more sense, as generally an IC will link to some IF, as OC relates to D.

The example activity you cite is very interesting for its completeness.

@notshi
Copy link
Collaborator

notshi commented Jan 5, 2019

Thanks, @stevieflow.

We're currently ordering them by transaction type code according to the standard; 1 - 13.

If we are to move code 11 before code 1, how should the rest be ordered?

@stevieflow
Copy link
Author

Thanks @notshi

Yes, understood. Transaction Type 11 (Incoming Commitment) was added in a later version of the standard, hence why it has a latter code. It "pairs" well with Incoming Funds, so I think it's an isolated case to reposition

NB: There is also the Incoming / Outgoing Pledge types, added in a later version of the standard. However, I think it'd be OK to leave those to 12 & 13, for now

@notshi
Copy link
Collaborator

notshi commented Jan 5, 2019

Thanks, @stevieflow - Transaction type 11 is now positioned above type 1.

@notshi
Copy link
Collaborator

notshi commented Feb 17, 2021

Closing this as resolved.

@notshi notshi closed this as completed Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
SAVi
Other TO DO
Development

No branches or pull requests

4 participants