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

Suggestion: Record Statistics #18

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 2 comments
Open

Suggestion: Record Statistics #18

GoogleCodeExporter opened this issue Mar 14, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link
Collaborator

Worship team has been asking me to create a way to record statistics of songs 
sung in our church.

I'm not a Java developer, so the suggested was to use a simple spreadsheet, 
however it is not working very well because they forget to update it;

I'm not sure how Datasoul works with the XML files, but maybe you could add two 
columns in the file:
1- (integer) Number of times the song was "used"/sung;
2- (date) Last time the song was sung;

OR you could use SQLite <http://www.sqlite.org> to record better statistics;

Thanks in advanced for your help and have a blessed 2013,

Douglas

Original issue reported on code.google.com by [email protected] on 23 Dec 2012 at 3:20

@GoogleCodeExporter
Copy link
Collaborator Author

There are a few issues with this approach, specially when you edit services in 
multiple computers. 
Maybe a better approach would be create an external tool that read a bunch of 
files from a directory and then generate the desired statistics. So, you can 
save in a directory all files you have actually used and then use the tool on 
it.

Original comment by [email protected] on 28 Dec 2012 at 2:06

@GoogleCodeExporter
Copy link
Collaborator Author

Original comment by [email protected] on 23 Jan 2013 at 8:04

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

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

1 participant