Custom content center library - Available for all projects new & old?

[henryjoseph9804]

Hi Everyone, 

I have just created a custom library on content center and published a part to it. The problem i am currently facing is that the library is only available for the project that I had active when creating it, I would like this library to be available for all future projects that are created and if possible for all existing projects.

How do I go about editing the library to allow it to be available for all projects?

Thanks 

[dave.cutting]

Hi,

Are you using a seperate project file for your individual projects? If you are then you'll have to configure each individual project to pick up your custom library.

If you go Get Started --> Projects, there is a configure content centre libraries icon on the bottom right hand side. You can enable your custom content centre file there.

[henryjoseph9804]

Hi Dave,

Thanks for the reply, that is unfortunate. i thought there would be a prompt of some sorts i could use to have this library available for future projects without having to toggle it in every time. Kind of like the standard content center.

[CCarreiras]

Hi!

Able your library in each project.

[henryjoseph9804]

Hi @CCarreiras Thanks for the reply, I can definitely do that, but is there no way to permanently enable it for every project created in the future?

[CCarreiras]

I have several project files as template, with different configurations.
Every time i need to create a new project file,  i copy a template project to the new project folder, rename it and double click to open Inventor with the project active.

[henryjoseph9804]

@CCarreiras, I'm intrigued!

So you literally just create a dummy project that has all the relevant workspace search paths and library and you just copy that and rename it to a more relevant project for your clients and then all everything is there without having to dictate it?

While after this the dummy still exists?

I assume that you just use Windows to ctrl+c & ctrl+v for the template project??

[CCarreiras]

Yes, something like that.
The templates are pré-prepared for several usual situations i need.
I go to the "project" templates, and copy paste rename to the new work folder.

[henryjoseph9804]

And do you use windows to do all the copy & paste?

[blandb]

Use a single project file for all work. Then you will only need to modify once and it applies to all jobs at that point.

[johan.degreef]

---

@blandb wrote:

Use a single project file for all work. Then you will only need to modify once and it applies to all jobs at that point.

---

If you are not using Vault, I would NOT do that.

[Frederick_Law]

---

@johan.degreef wrote:

---

---

If you are not using Vault, I would NOT do that.

---

I was not using Vault for over 20 years and I did that.

With 6 other in one company.

My folder structure is Vault "compatible".

[blandb]

Not to get off topic here, but I have only ever used Vault, but still don't see a reason why that is a bad idea. The only time we have ever needed to switch a project was due to the fact that we could not have "cross contamination" of Content items. We were suppled a specific set of libraries and templates that needed to be separate. So, in that sense...sure. But if you use the same CC, templates, etc from job to job. I don't see the advantage of using independent projects for each job. One location for your jobs, one project file to deal with, one set of templates, etc. In this case, his issue is solved, all current and old jobs would have what is needed.

[Frederick_Law]

In the beginning, multi-project file was recommended.

Later, single was recommended.

I used single project since R5.3.

Worked with Vault on R9 and setup folder structure so Vault and Pack-n-Go got similar structure.

I moved everything under same folder: CC, Degign Data, Template etc.

Very easy to transfer to another computer.

[henryjoseph9804]

Thanks for the response, I can definitely see how this would streamline the repetitive tasks, I feel comfortable keeping it to different projects just to prevent parts from different projects being used in the incorrect project.

[henryjoseph9804]

I hear you, Would it not cause trouble if you use a common naming methodology? For instance project A has part 1 and Project B has Part 1, would this not lead to confusion??

[Frederick_Law · Accepted solution]

It'll will, so no duplicate names.

IV will work with duplicate filenames.

Problem start when you open assemblies that use same file name.

First one will replace second one.

A file naming system is needed.

And Vault will enforce no duplicate names.

I use project name/job number + part number.

Order/job number works well in most company.

Order number: 71565856-

Part Number: 00-00-00

00- is assemblies

Next 00- is sub-assemblies

Last 00 is parts

Use 000 if you have more parts.

Descriptive file name works until a plate become a bracket.

When design parts, I don't want to decide what they are when I need to save the file.

Some may not go to production.

[henryjoseph9804]

Thanks for that explanation pineapple, I see what you mean now.