UseMod Wiki: TextFormattingRules

Rubyforge projects use this wiki engine. UsedMod

Its a bit different from wikipedia (media wiki) and therefore, one might have to carefully look at the formatting tricks and tips.

Here’s some help.

UseMod Wiki: TextFormattingRules

Blogged with the Flock Browser

Adding pages to your rubyforge website

Thanks to Tim Hunter for guiding me to the faq to be able to post pages on the project website.

http://rubyforge.org/docman/view.php/5/460/faq.html

Registered at Ruby forge

The Library Mananagment System project has been registered at RubyForge. You can access the default project page at http://rubyforge।org/projects/lms
.

In coming days, I am going to explore more about the project setup on ruby forge and then update accordingly. Right now, the default virtual host that we have got is called http://lms.rubyforge.org, but it really is the default page.

Would update more, perhaps post the few pages that I have thought of on the wiki there.

Classes for Library…

More on the Library Project

Was thinking further on this and found a basic idea of the classes I would see..

1. Book
1. Properties
1. Id
2. title
3. author1
4. author2
5. author3
6. isbn no
7. language
8. type
1. printed matter [default]
2. dvd
3. CD
9. meta tags [comma delimited]
10. year of publishing
11. edition #
12. issue cycle (days)
13. No of copies
2. Methods
1. add
2. remove
3. update
4. add a copy
2. Lib Transactions
1. Properties
1. date of issue
2. member id
3. book id
4. date of return
2. Methods
1. issue book
2. return book
3. Member
1. Properties
1. Name
2. age
3. address
4. sex
2. Methods
1. Add
2. delete
3. update

Would update more…

Library Management System : Ruby on Rails

Well, I want to learn some more of rails and ruby (as much comes along).

And so I thought of building a tiny little web application to build a library management system based on rails and mysql.

The idea is that, it would be a web based application to manage the library from an staff member’s point of view. At a later stage, there would be an additional viewpoint from the library visitor, to search for books, request for issue etc…

I also intend to build a page which could be used to issue out or receive books (as a library transaction).

Here is a summary of what I have thought this application would do.. to start with…

1. Keep stock of books
1. multiple copies of book allowed
2. Allow searching for books in library
3. search on meta tags
1. Title
2. description
3. author
2. allow books to be issued out.
1. keep track of date of issue
2. Expected date of return
3. Administration
1. Allow to add books
2. Rename, replace, add remove copies etc.
4. Reports
1. Books overdue on a given date
2. Members with overdue books
3. Books that are most probable to go overdue
4. Members most responsible for overdue books
5. etc…

Well, thats the very first stage of requirement thinking that has been done.