ncs-jss / http_200 Goto Github PK

Database tables needs to be filled with sample data before testing the application. We have a lot of alternatives to fill the database. Some of them are:

1. https://github.com/kaleidos/django-sampledatahelper
2. https://github.com/aerosol/django-dilla
3. http://www.generatedata.com/

Suppose admin wants to export the data of students of a particular class or any group of students, then he can have the export csv option on the django admin panel.

Create the faculties and students from the django admin through a single page with three fields username, password and group where group will have following choices:

1. Student
2. Faculty
3. HOD
4. Management
5. Other staff

We should show a dialogue box when the faculty wants to delete the notice.

The BranchYear table is not filled up when the notices are created. The form_valid method should be overriden so as to get this working.

This involves:
a) Create backend logic for creating a new user
b) Create a template for the same

We need to have a discussion that should we use the django admin or we should create the templates by our own.

Look at http://ckeditor.com/demo#standard for more details.

For instance a HOD should be able to send private notices to other faculty or other HOD or to all the students. In general, we need to create a private way of sending notices.

Once the user is created by the admin and as the user arrives the login page and tries to login then he should be redirected to the "complete your profile" page. After successfully filling the details, then only he can go ahead and perform the further transactions.

@Shivam1904 can you help me with this? it seems that the README is outdated and if someone wants to setup the repository on his local machine then he cannot do that.

Why so?

This issue involves creating a dump of the old information center and then merging the data into a single table. We need a python script that do all this task.

The old table has two different tables:

1. Only Notices
2. Only Downloads

But we are merging these two into a single table in the current version i.e v1.1

Certain user might wish to keep a Bookmark at top so he has to not scroll down. So we can have this enhancment feature same as FB.. Pinning the bookmark to top. It can be for later version if not right now.

Currently, when we are creating a notice then we run the following queries:

`

Notice.objects.create(...)

for i in branch:
    for j in year:
        NoticeBranchYear.objects.create(...)    

`
I think this will make our system really slow and we should optimize this.

What I have in mind right now is adding two fields in Notice table:

1. Branch(CharField)
2. Year (CharField)

where both will store the Branches and Years separated by spaces like Branch = CSE IT ECE EE and Year = 1 2 3 4

@shriyanka @Shivam1904 @Curious72 @abhisheksachan need your reviews guys.

For every user, we need to have a last_seen feature. This will include two types of messages:

1. Read messages
2. Unread messages

We need to maintain these two categories for every user.

The usecase is that every user can bookmark any number of notices and we need to create a new Model for that named BookmarkedNotice that contain two fields notice_id(fk) and user_id(fk) so that later on we can show the filtered list of notices.

For reference : http://django-spaghetti-and-meatballs.readthedocs.org/en/latest/installing.html

For reference, visit http://daler.github.io/sphinxdoc-test/includeme.html

For reference: #68
@Shivam1904 do ping me if you need some help or any clarification.

As discussed with @deshraj we will be creating a smooth admin interface for all app and its admin so that system administrators do not find it difficult to add new entry in the database.
This is as per current discussions we can change it or see what is required for version v.2 onwards.

Currently assigning it to my self. If any one else is interested to work on it feel free to leave a comment.

for further understanding refer Closed Pull Request #53

We have two categories and permission levels , Students and Faculties.

Now, we need to add more categories namely

1. Student
2. Faculty
3. HOD
4. Management
5. Other Staff Members

Also we need to assign permissions to these categories.

Create the djangoapp named Notices for performing the CRUD operations on notices that are being uploaded.

we can use django-filter for the queryset filtering dynamically and that will be really easy to the users to filter the notices.

If someone is uploading the notice, then he/she should be able to set the option that whom he/she wants to send the notice. It may be specific to HODs only, Principal only or public and many more.

Username, First Name, Last Name, Email are missing.

Write tests for the profile app so it covers the usecases so that after we can integrate Travis CI for continuous integration. @Shivam1904 Can you look into this ?

On /user/student/, when we try to edit the course, university_roll_no or the contact_no, then the updation is not happening properly. @Shivam1904 can you fix this as you were working on this ?

Can we please make a single permissions.py file for HTTP_2OO rather than making separate individual permissions.py file in individual apps.
This would require extra work of code cleanup in individual apps but would be great.
Suggestions @deshraj @Shivam1904