Skip to main content
Solved

Does anybody have any documentation on best practices for repository naming and permissions?

  • September 15, 2016
  • 1 reply
  • 66 views
J

Hi,

As of late I've noticed that we've got a lot of sprawl with the names of our repositories. Does anybody have any best practices/recommendations on how their organization creates repositories/topics/notifications and assigns permissions?

One thought I had was to create a repository per application and also per department/organizational group as needed. But I'm wondering if anybody else has any other ideas/thoughts on the matter. In addition, my thoughts really only apply to repositories and don't take into account permissions/topics/notifications.

If it matters, my FME Server install only runs on my intranet. I don't need to expose it to the public.

Thanks!

-Jeff

Best answer by redgeographics

Overall the "rules" that you would apply to naming directories on a local filesystem can be applied to repositories in FME Server. Per application/project and per department is probably the best way to go. I would recommend trying to settle on a standard naming scheme that matches your network file/directory naming conventions to avoid that sprawl and carry that naming scheme on to the workspaces in the repositories and the notifications/topics as well.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

redgeographics
Celebrity
Forum|alt.badge.img+60
  • redgeographicsCelebrity
  • Celebrity
  • 3704 replies
  • Best Answer
  • September 15, 2016

Overall the "rules" that you would apply to naming directories on a local filesystem can be applied to repositories in FME Server. Per application/project and per department is probably the best way to go. I would recommend trying to settle on a standard naming scheme that matches your network file/directory naming conventions to avoid that sprawl and carry that naming scheme on to the workspaces in the repositories and the notifications/topics as well.

FME rocks! \m/

Community Stats

32,100
Posts
121,893
Replies
39,744
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.