Page Comparison

...

Table 1.

Locationable

Locationable entities can have one or more LocationData objects in their list of locations.  LocationData is the precursor to our currently supported FileHandle.  Each LocationData object points to either object in S3 (like a S3FileHandle) or an external URL (ExternalFileHandle).  Most of the client support burden is around supporting Locationable Entites. Table 1 shows which entity types are Locationable.  Even though a Locationable can have one or more LocationData it is assumed that each LocationData represents the same file just store in alternate locations and that all "copies" have the same md5 (see Figure 1).

...

In order to fully depreciated the unsupported types, we need to convert each old type objects into one an object of the supported types (without changing the entity ID).  The plan is to add a new services that will convert an old entity to a new type.  Many conversions will be simple.  For example, it will be simple to convert a a data object with a single file.  Conversion will not be simple for all cases where there is not a one-to-one relationship between the old and new.

Response codes:

The following table lists how each old type will be converted into a new type. 

Note: Any deprecated entity fields with values (see Table 1 'Deprecated Entity Fields')  will be preserved as annotations on the new entity.   Any non-primitive deprecated field will be saved as a string annotation.