A couple of questions about MediaBin 4.6

System

I have a couple of questions about the 4.6 upgrade. I'm posting them here because I believe that other people might be interested in the answers.


TeamSite Connector: will there be a TeamSite connector from MediaBin 4.6 to Teamsite 6.5?

Hot Folders: will Hot Folders still be part of MediaBin? Will we have to redefine all Hot Folders as it happened when we went to 4.5?

Deployment Agent: will it still be there? Will we have to redefine all Deployment projects or will it be a simple upgrade?

API: any major changes to Web Services and / or COM API?

Thanks in advance...

Migrateduser

I can speak to DeploymentAgent and the COM API. There will be a DA 4.6. The changes are minor: encryption of the DSN for the SQL database, support for file sizes larger than 4GB, the following changes to the search operators (which apply to all client products):
- removed NotContains operator for metadata of type "array of string"
- removed the following operators for "any text" type searches:
- not equal, not contains, not starts with, exists, not exists
- only the following operators are available for "any text" type searches:
- is exactly, contains, starts with

There were no database schema changes for DA 4.6 from the 4.5.3 version. You may need to manually adjust your search operators if you're using any that are affected by the above changes. If you're not searching for "array of string" type metadata and not using "any text" type searches, no changes should be required.

Per the COM API, the changes are minimal and probably won't affect any of your existing script. The changes are numbered below.

1. There are two new search operators available for "quick search" type searches: "ContainsWord", "NotContainsWord"

2. Three methods of the MBContainer object have been extended for pagination. Note, the new parameters are optional with defaults that effectively disable paging, so no changes should be required to existing script. Below is a snapshot of the IDL for those three methods:

HRESULT ContainerChildren([in, defaultvalue(VARIANT_FALSE)] VARIANT_BOOL ReturnAll, [in, defaultvalue(VARIANT_TRUE)] VARIANT_BOOL IncludeDeletedItems, [in, defaultvalue(InfinitePageSize)] long PageSize, [in, defaultvalue(NameMetadataGUID)] BSTR SortId, [in, defaultvalue(VARIANT_TRUE)] VARIANT_BOOL IsSortAscending, [out, retval] IMBObjectCollection **pVal);
HRESULT AssetChildren([in, defaultvalue(AllAssetItems)] MBRepositoryItemType Type, [in, defaultvalue(InfinitePageSize)] long PageSize, [in, defaultvalue(NameMetadataGUID)] BSTR SortId, [in, defaultvalue(VARIANT_TRUE)] VARIANT_BOOL IsSortAscending, [out, retval] IMBObjectCollection **pVal);
HRESULT ImageChildren([in, defaultvalue(InfinitePageSize)] long PageSize, [in, defaultvalue(NameMetadataGUID)] BSTR SortId, [in, defaultvalue(VARIANT_TRUE)] VARIANT_BOOL IsSortAscending, [out, retval] IMBObjectCollection **pVal);

3. One method has been added to the MBObjectCollection object to further support pagination. It is used to locate the position of an item, by Identifier, within a paged collection. The client uses it to display a page containing a single asset after the user has performed an operation on that asset that may have caused a resort (so the items may have moved around to different pages).

HRESULT GetPagedItemIndex([in] BSTR Identifier, [out, retval] long *pIndex);

4. A new method has been added to the MBJob object to get the name of the asset associated to the job. The FileName method is still available but may return GUIDs if insertions were done using the mac native client.

HRESULT AssetName([out, retval] BSTR *pVal);