The document discusses the Virtual Research Environment for Cancer Imaging (VRE-CI) project which aims to provide a framework for researchers and clinicians to share cancer imaging information, images, and algorithms. It describes using Business Connectivity Services and managed metadata to organize and search image metadata, and building a reusable SharePoint site definition to manage DICOM files and extract metadata for search. Key aspects covered include mapping folders, issues with document library names, including external code, and adapting the DICOM field model.

1. A Virtual Research Environment for Cancer Imaging (VRE-CI) British Library – RIC Workshop 22 March 2011

2. Outline VRE-CI Project Manage Image Metadata Using Business Connectivity Services (BCS) Building the VRE-CI Site Template

4. JISC VRE frameworks phase 3.

5. 22 months 01/05/2009 – 21/02/2011.

6. Project Partner: Microsoft Research

7. Lee Dirks

8. Alex Wade

9. Roger Barga

10. Team members:

11. PI. Prof. Anne E. Trefethen

12. Co-I. Dr. Vicente Grau

13. Project Manager Dr. M. Susana Avila-Garcia.

15. DICOM Image Viewer

16. Manage Image Metadata All of the images in the document set share the common metadata

17. Manage Image Metadata These fields are the Managed Terms which can be modified by users

18. Manage Image Metadata Managed Terms is stored in the Taxonomy Term Store in the Managed Metadata Service

19. The Image Metadata can be used for... Filtering images

20. The Image Metadata can be used for... Grouping images

22. SharePoint Designer 2010 BCS Solution to Access Trident Registry Add a new External Content Type

23. Connection to Trident SQL Server

24. Create Operations on “Activity” table

25. Create Filter Parameters

26. Create External List

27. Retrieve Trident Registry Information Trident Workflow Information

28. Visual Studio 2010 BCS Solution to Access Remote Image Metadata User Case: Unix file storing system in ROB Large volume of files Raw data containing no or less meaningful metadata Using a specific folder structure to indicate the image metadata e.g. Technology, Image Acquisition Machine, Group Head, Users. Allow SSH to the file server

29. Folder Structure Example tomography Systems Inveon MRI47 Data Data RM1 RM1 SF1 SF1 RM1_SF1_SF36_420 RM1_SF1_SF36_420 20100223_static_VCAM_tumour_M1_5hpi 20100223180102_01

30. Image Metadata Retrieved: Technology: Tomography Image Acquisition Machines: Inveon; MRI47 Group Head: RM1 User: SF1 Study Nameumber: RM1_SF1_SF36_420 DataSet Name: 20100223_static_VCAM_tumour_M1_5hpi; 20100223180102_01

31. Solution Shell script to populate the image metadata XML Use SSH to transfer the image metadata XML to the SharePoint Server Apply Business Data Connectivity Services to connect SharePoint to the external image metadata XML Navigating and searching the image metadata within SharePoint

32. Business Data Connectivity Model template

33. Edit TypeDescriptor Xml

34. Implement ReadItem & ReadList Methods in the service class

35. New External Content Type Created in BDC Service

36. Create External List

37. ROB Image List in SharePoint

38. Aims A reusable site definition for SharePoint to manage cancer related DICOM files. Make visible the metadata from inside the DICOM files within SharePoint. Especially within Search. Enable areas of the DICOM files to be marked for subsequent analysis. To link with Trident for subsequent analysis

39. Visual Studio 2010 The definition is built using Visual Studio XML, C#, SharePoint APIs, Silverlight APIs

40. Creating a new site from a site definition

41. Site provisioning SharePoint ‘provisions’ a new site from a site definition. This requires the site definition to have to perform various actions – in the right order: Global onet.xmlThis file defines list templates for hidden lists, list base types, a default definition configuration, and modules that apply globally to the deployment. SPSite scoped features defined in site definitions onet.xml, in the order they are defined in the file.The onet.xml file defined in the site definition can define navigational areas, list templates, document templates, configurations, modules, components, and server e-mail footers used in the site definition to which it corresponds. SPSite scoped stapled features, in quasi random order SPWeb scoped features defined in onet.xml, in the order they are defined in the file. SPWeb scoped stapled features, in quasi random order List instances defined in onet.xml Modules defined in onet.xml [Source: Site Configurator v2: User Guide for Developers] This is frustratingly easy to get wrong!

42. Site Configurator To help build the definition we used the SharePoint Site Configurator Feature http://spsiteconfigurator.codeplex.com/ (January 2011) This enabled simpler ‘provisioning’

43. Useful techniques: mapping folders

44. Issues with document library names Site Configurator does not deal correctly with spaces in document library names for provisioning. Best to avoid spaces. Thicket folders: folders ending in ‘_Files’ and a host of other similar names are hidden/renamed by SharePoint. See KB905231. This ‘feature’ directly interacts with the DeepZoom technology, which uses ‘_files’ as a suffix for a directory.

45. Including external unmanaged code Technically tricky: avoid if at all possible Map C:rogram Filesommon Filesicrosoft Sharedeb Server Extensions4IN and place unmanaged DLLs in it. Use managed code to call the unmanaged code. E.g. [DllImport("DICOM.dll")]

46. DICOM types DICOM has approximately 3500 field types – identified by their Tag name which has the form (Group, Element). We adapted the IETF RFC4122 name-based GUID algorithm (section 4.3 of http://www.ietf.org/rfc/rfc4122.txt) to map these onto SharePoint Field definitions with name based GUIDs, and generated corresponding fields within the site definition. An example generated field is: There can be issues when re-loading fields into SharePoint. It worked first time isn’t good enough! We found that the above form worked the second time as well. The key extra attribute is ‘DisplaceOnUpgrade’.

47. Things we would do differently Use the Silverlight client object model Prefer ‘Plain Old Document Libraries’ over Document Sets until they are more mature Separate the DICOM field definitions from the site definition during development (they take an age to load on a development VM) Consider recoding some of the ‘Untrusted code’ as trusted code.