"Learning Objects" app about lore HOT 11 CLOSED

Django uses integers as primary keys by default. I prefer the use of a uuid4. Is this worth considering for these models? It prevents confusion and conflicts during import, export, and distributed storage.

from lore.

I'm not sure about the implications in Django but I like the idea and we need uuid-s - It's currently separate from the primary key https://goo.gl/gmpedb.

from lore.

In the past, I've subclassed Django's models.Model to one that automatically uses UUIDs as the primary key, and automatically stores the date created (auto_now_add=True) and the last modified date (auto_now=True). Also, a "notes" field about any modifications made by admins, and foreign keys to the user who created and last modified them.

(Then used this model everywhere instead of models.Model).

from lore.

That sounds good for inheriting from a common model with extra fields. A question about the database model, is uuid in the diagram supposed to be equivalent to the OLX "url_name" that is often, but not always, a uuid? If so, we need to make sure that we don't use that uuid as a PK since there will be duplicates among different courses, and xbundle, for example, will strip those out and replace them with "human readable" IDs. If it isn't, what is the difference between the loid and the uuid, shouldn't both of them uniquely identify an object?

from lore.

Some say it's tricky in Django: http://stackoverflow.com/a/3944247

from lore.

@carsongee, in the current diagram uuid is machine generated.

from lore.

Some details about the LearningObject schema :

from lore.

I'm changing some of the field names:
https://gist.github.com/trski/6ea8c8afb4f783c71b42
Just included some '_' for readability for the python variables and changed 'when' to 'date' so we know the field is a date type.

from lore.

👍

from lore.

I believe this was closed by #10. @Ferdi are you OK with that?

from lore.

I think it's good for now. We can always open new issues for improvements / fixes.

from lore.