Skip to content
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.

Implement the budget system #35

Open
Xiphoseer opened this issue Apr 22, 2017 · 2 comments
Open

Implement the budget system #35

Xiphoseer opened this issue Apr 22, 2017 · 2 comments
Milestone

Comments

@Xiphoseer
Copy link
Member

We planned and need a system that allows us to keep track of the amount of money that we spent. We have the data fields for that, but we can not really rely on any prices we know in advance. Need some input to figure this out.

@Xiphoseer Xiphoseer added this to the SoSe17 milestone Apr 22, 2017
@Xiphoseer
Copy link
Member Author

I honestly have no clue on how useful a thing we can implement here. As long as we do not have real prices, we have to keep our eyes on that anyways.

@Xiphoseer Xiphoseer mentioned this issue Apr 22, 2017
@akwick
Copy link
Collaborator

akwick commented Apr 22, 2017

One suggestion is that we rely on
a) the prices we obtain when we order
b) in the time between two orders, we rely on the prices stored in the books
c) when we reach an amount which is e.g. 10 % less than the budget, we can give the student a warning that it could happen that not every order can be processed anymore [0]. This should be fine as the library, will reject orders when we are going to exceed our limit. Further, when we receive a mail, we can react and can talk with the mint team of our library.

If we reach c) and have spent all our money on the budget and then, we can e.g. stop the order process by ending the ordering frame. Is that possible? Another alternative would be to somehow explicitly end all orders for the term (a simple boolean value).

I think that should okay as we have never exceeded the limit since I am part of the team.

[0] This also can happen if someone orders a book which already exists in a large amount in the library. So this should be fine.

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

No branches or pull requests

2 participants