angusglchen/delftx-database

delftx-database's Issues

Removing deleted elements

In course structure, some elements have creation time earlier than the course start time. In our initial code, we remove them since some of those contents are treated as "deleted".

However, some of them are reserved in the course running. Actually, we cannot justify if an element is deleted or not, just based on their creation time.

If there is a clear tag which shows whether those elements are deleted or not, it would be better.

Otherwise, we have to keep all of those elements and treat them as elements created in the first week.

The Question of this issue is that do we have a clear tag to show elements deleted or not in course structure file?

Python 2/3 compatibility

Right now, the project seem to work only with python 2. there is no strong reason why this should be the case (usually, restricting yourself to python 2 is the result of urgently requiring a library unavailable to python 3).

Therefore, the code in this project should be as universal as possible. You can easily do code which runs on both python 2 AND python 3, instead of code which runs only on 2. Just use the proper syntax for problematic calls like print('test') instead of print 'test'.

There is a tool called 2to3 which can convert code automatically (it is automatically installed). see here: https://docs.python.org/2/library/2to3.html

I do see no reason for this project to use outdated coding convents which only run on outdated interpreters.

Project Structure

Hey,
we should opt for a more collaboration-friendly project structure, e.g., see here: http://docs.python-guide.org/en/latest/writing/structure/

At least we should either have a requirements.txt, or setup.py (personal preferences, we can also do both).