We would like the creation of a tab called "Category Images" and follow the same code for uploading product images.  

Under a general category, we have many similar products  that all use the same images.  It would be easier management with less DB space if we could upload multiple category images and only one particular product image.

On the menu strip: Edit Category Details - Add tab "Category Images"
   (use same code as "Edit Product Details" --> "Pictures" tab to upload multiple images

At Public Storefront click on Category Group.  Just below the Category description, show the image strip, then products below the general image strip.  (an example of image strip is shown under Product Details.)

Database would need the following table (sql code below):Category_Picture_Mapping
---------------------------------------------------------------
USE [dbname]
GO

/****** Object:  Table [dbo].[Category_Picture_Mapping]    Script Date: 12/10/2011 12:47:52 ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[Category_Picture_Mapping](
  [Id] [int] IDENTITY(1,1) NOT NULL,
  [CategoryId] [int] NOT NULL,
  [PictureId] [int] NOT NULL,
  [DisplayOrder] [int] NOT NULL,
CONSTRAINT [PK_Category_Picture_Mapping] PRIMARY KEY CLUSTERED
(
  [Id] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]

GO

ALTER TABLE [dbo].[Category_Picture_Mapping]  WITH CHECK ADD  CONSTRAINT [FK_Category_Picture_Mapping_Category] FOREIGN KEY([CategoryId])
REFERENCES [dbo].[Category] ([Id])
GO

ALTER TABLE [dbo].[Category_Picture_Mapping] CHECK CONSTRAINT [FK_Category_Picture_Mapping_Category]
GO

ALTER TABLE [dbo].[Category_Picture_Mapping]  WITH CHECK ADD  CONSTRAINT [FK_Category_Picture_Mapping_Picture] FOREIGN KEY([PictureId])
REFERENCES [dbo].[Picture] ([Id])
GO

ALTER TABLE [dbo].[Category_Picture_Mapping] CHECK CONSTRAINT [FK_Category_Picture_Mapping_Picture]
GO
------------------------------------------

I greatly appreciate anyones help in directing us to the right locations to edit the source code to allow for this feature.
Thank you,
Geoff