Martin Dougiamas

There are so many application profiles ...

http://en.wikipedia.org/wiki/Learning_object_metadata

But some Moodlers have defined one called MoodleCore:

http://docs.moodle.org/en/Development:Metadata

Shall we go with that?

I'm just a bit worried that a form with all those fields will just be way too confusing for ordinary teachers to use.

Thanks Jonathan, good point that we should be storing outcomes and allowing searches on them! I've added that to the spec.

Yes, +1 for Tim's idea here.

This sounds like a good idea in that it makes the code shorter (and hopefully faster to write!) without losing readability.

Perhaps $DB->must_get_record() works better as a name (or family of names if this is going to be replicated consistently for other $DB->get functions).

I do see Eloy's point about the purity of the class, but I think if we see these as "add-ons" to DML then it's OK with me. The point of an API is to be as useful as possible after all.

We have some dilemmas with an interface here in Moodle 2.0 for managing media files within HTML documents.

I would really like your feedback and extension to the ideas here to help us decide the best path:

http://docs.moodle.org/en/Development:Editor_file_management

Feel free to add new ideas to the document or just reply to this discussion.

Thanks!