My question was, "What's the intended difference between display_coursenum
and display_name." I still don't understand. Are these intended to be used
in different contexts? I would think that a course's display name is its
display_coursenum. perhaps it's just my rejection of a universal notion of
course number which I think of more as course short name but some
institutions (MIT) use numbers.

The org statement was that we should have a separate collection which
defines orgs including their display name, brand image, who admins their
namespace in edx, etc. If display name is defined per course, it will lead
to inconsistencies. However, all we should do now is record the story not
design around it.


On Thu, Nov 7, 2013 at 1:35 PM, chrisndodge <notifications@github.com>wrote:

> In docs/internal/edx-mobile-api.md:
>
> > +	"status": "error",
> > +	"err_type": "UserNotEnrolled"
> > +	"err_msg": "User is not enrolled in course"
> > +}
> > +```
> > +
> > +##### Get list of enrolled courses for user
> > +
> > +**Request: HTTPS GET /edx-mobile-api/v1/registrar/get_enrollments_for_user**
> > +
> > +Note: Requires authentication token passed in the headers as indicated above
> > +
> > +**Response: success**
> > +
> > +```
> > +StatusCode: 200
>
> display_coursenum, display_courseorg was introduced a few months back
> mainly because the course_id from which we parse (and use as display
> strings) part of the URL. This doesn't work well for other languages, both
> the QRF (arabic) and XuentagX (Chinese) need to have a means to separate
> the display side of a course number and organization.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/1609/files#r7505229>
> .
>