Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Best Way to Access Separate Core Data Document

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Best Way to Access Separate Core Data Document

Subject: Best Way to Access Separate Core Data Document
From: Marc Blatt <email@hidden>
Date: Sat, 21 May 2005 21:19:45 -0700

We are looking to implement a Core Data Document Based Application (the "User App") where the user can manually enter their research data and also be able to build their reference materials from a separate, read-only Core Data SQLite or Binary Document or a Core Data Application (the "Ref App"). Although Services could be used to accomplish this, we do not want the data being provided outside of the User App for confidentiality reasons.

The Ref App data will be managed and updated by a single department. Since there will be a fairly large amount of info in the Ref App, it would be nice if the User App could drill down to the relevant material either through a Bundle that accesses the Ref App data or by searching the SQLite or Binary file directly from the User App. The Ref App will be a different Core Data Model than the User App.

The User App would provide search fields and/or a series of ComboBoxes that create subsets of data from the Ref App File or the Ref App directly for each ComboBox until a manageable set of data is displayed either in a NSTableView or NSOutlineView.

A simple example:

User enters a year in ComboBox A, ComboBox B is now populated with the months that data actually exists in the Ref App File or Ref App;

User selects or enters a month from ComboBox B, ComboBox C (if the month exists in ComboBox B) is now populated with Information Categories available for the specific month and year selected in the Ref App File or Ref App;

User selects category from ComboBox C, an NSOutlineView is now populated with confidential data files from the Ref App File or Ref App for that category, month and year;

User selects a confidential data file from the NSOutlineView, selected data is entered into the User App for reference--it is not a pointer to the read-only data, but is actually copied into the User App file.

(Note: Don't worry about the confidential data being copied over, certain fields will not be copyable; we have a handle on that aspect. Also, you can assume that everyone that has access to the User App has clearance.)

We would appreciate any thoughts on the best approach to implement the pipe between the User App and the Ref App or Ref App File. _______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden Follow-Ups: Re: Best Way to Access Separate Core Data Document From: mmalcolm crawford <email@hidden> Prev by Date: Re: User Authentication Next by Date: Re: Best Way to Access Separate Core Data Document Previous by thread: Re: Automatic build number incrementing Next by thread: Re: Best Way to Access Separate Core Data Document Index(es): Date Thread