NPO-Accounting/npo-accounting-ikiwiki Changeset - 6d09a3097f69

Changeset - 6d09a3097f69

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Brett Smith (brett) - 8 years ago 2016-09-02 15:41:48
brett@sfconservancy.org

Add Desired Features section with iCalendar export.

1 file changed with 19 insertions and 0 deletions:

Reimbursements/Requirements.mdwn

0 comments (0 inline, 0 general)

Reimbursements/Requirements.mdwn

➞

Show inline comments

@@ ... / @@ -219,14 +219,33 @@ effort for the first release. @@
   rates might be available via an API somewhere, and we can use that to have
   the requestor give us "preferred currency for payment" so all changes
   happen in real time in the interface (even allowing the requestor to be
   able to decide *while filling out the report*: "ugh, these exchange rates
   to INR are horrible; I'll have them pay my USD account instead").
 ## Desired features
 These are features that we would also, ultimately, like the system to
 have.  But they're not as critical as the features in the previous
 section, and they don't need to hold as much sway over the choice of a
 base system or framework.
 * Data import
   * Apps like [Tricky Tripper](http://trickytripper.blogspot.de/) let users
     track expenses for a trip as they go.  The system could import this data
     to prepopulate answers to questions about the request and expenses in
     it.  Probably there would be an import API that can map different import
     formats to a common format, and then administrators can define how
     questions in their system can be answered based on imported data.
 * Provide iCalendar feeds for request-related tasks
   We could implement any combination of the following:
   * Each request has its own iCalendar feed
   * Each user has their own iCalendar feed, which includes tasks for
     all the requests they're involved in
   * Each user has their own iCalendar feed, with deadlines aggregated
     within it (e.g., "3 requests outstanding more than 60 days")

0 comments (0 inline, 0 general)