Looking for suggestions to help my project work-flow.
How can I “connect” info across databases?
Simple example is that I have one database with “Base” material which I create, and a second “Project database” for ongoing work. Many times I want to use a document from the “Base material” database in a project located in a “Project database”.
Assuming no changes to the document, how could I have some type of entry in the Project database that connects to the document in the “Base material” database? Do I need to create a text file that includes a DTP link to the document in the “Base material” database?
I appreciate any and all suggestions for how others accomplish something like this.
Thanks for the suggestion DTLow - I have considered that.
Typically I have five or six current client projects and scores of closed client projects. I’m trying to have the closed projects archived in yet another DB so they don’t clutter up my navigation, searches, etc.
Generally, the docs in the Base materials are static but sometimes I may revise them independently or as a result of project work. For now, working with static docs will be a big help.
Blockquote * Would you be making notes about the document that only pertain to the project you’re working on?
I want to be able to quickly see all materials I am using and / providing on a project. In my mind, it would be like having replicants from another DB in the project DB. (but I know DT doesn’t do that). The only way I found is to create 1 RTF doc in the Project DB that contains DT links of the docs from the Base DB. That kind of gets the job done but then I need to open the RTF to see the list of docs and then find the way to the doc in the Base DB …
DT is so rich, I assume there is an approach to accomplish this but I haven’t found it yet.
As another suggestion, I guess you could also copy the item links and paste them into the project database as bookmarks. This might come pretty close to having replicants, if that’s what you’re looking for.
Thanks all for the suggestions. My take away - as I suspected DT dos not do what I was trying to accomplish, and probably with good reason. The option that gets me closest is just having copies of Base files in the Project DB.
And given your description, I personally believe this is the optimal solution. 32 years in graphic arts & printing taught me to create discrete structures that encapsulated an entire project, regardless if there was duplicate information. I could hand off any folder, CD, or hard drive knowing everything needed to reproduce that product was there.
I’m worried. Assuming you went to school before that, and adding the apparent lifetime you have worked for DT that’s scribbles 16 + 32 + lifetime = ancient! I hope you’re not considering bunking off on retirement any time soon?
I started in graphic arts professionally at 15 (yes, 15) and have no formal schooling in it. I’m a quick study and mostly self-taught. Also, I’ve been with DEVONtech 9 years this July but my time here overlapped with my previous job by several years.
Indeed, I am. I had one semester of art school and got kicked out of a 2 year graphic arts program after 1 year (partly because I had learned the two years worth of knowledge in the first semester, got a job running a printing press, and ended up teaching the other kids ). The tech stuff I taught myself to become more efficient in printing companies and service bureaus I worked at. (I was sometimes running three or four Macs simultaneously, i.e., multiple print jobs - usually catalogs - at once )