Project Naming Conventions?

Would anyone care to share the naming conventions they use for projects? I have a manageable number now so naming doesn't matter so much, but I can see having a large number of projects soon. Thanks!

Kenneth Kirksey wrote:
Would anyone care to share the naming conventions they use for projects? I have a manageable number now so naming doesn't matter so much, but I can see having a large number of projects soon.
hi, ken
do you have clients?
my folder/project naming conventions...
main subject with projects below
for example,
Beach (main subject)
Jetty (sub subject)
Nature (main subject)
Birds (sub)
Birds of Prey (sub sub)
Fashion (main sub)
Model Name (sub)
Calvin Klein (sub sub)
(MGM Grand) (sub sub)
Music (main)
Artist Name (sub)
name of Project currently working on (sub for artist)
I hide photos in yellow folders to keep other clients from viewing photos from others
sometimes 2008 Beach to keep the year separated
victor

Similar Messages

Problem with project naming

Have anybody managed to change the default project naming parameter? When I import my photos into a new project, the Aperture always name the new project like '16 Dec,2010', and I would rename it as '20101216' every time when I have finished importing. I don't want rename them any more.
So, how can I change the project naming format to something like '20101216' by default?
I've tried to change the Folder naming preset in Aperture menu, now my project naming format is 'ImageYear ImageMonth ImageDay', and the example shown above is '20080101', but when importing photos into new project, the new project still names as '16 Dec,2010' and the preset seems doesn't work at all.
Anybody knows how to deal with it?
(Now I've checked 'automatically split projects' in the import setting and set 'split projects by date' in preference.)
Message was edited by: bromoethane

When you import you can name the project you want to import into. Look at the right hand side of the import browser in the section labeled *Aperture Library*. You're destination can either be an existing project or a new project. If you select new project you can enter the name of the project.
Unfortunately I don;t believe that there is a way to change Aperture default project naming convention.

Versions naming conventions on Duplicate Project

I love adding "v001" at the end of project name, but when I duplicate the project:
[project name] v001
[project name] v001 1
[project name] v001 2
and I hope it will be:
[project name] v001
[project name] v002
[project name] v003
and I found if you fcpx just allow this naming convention
[project name] 1
[project name] 2
[project name] 3
and I thought it was the "v" problem, then I remove the v from "v001", it results:
[project name] 001
[project name] 2
[project name] 3
the "00" disappear! so will fcpx fix that? so I can use v001, v002 or someone v01, v02 or 001,002,003

Andy Scott3 wrote:
Maybe someone could help me out here.
In L7 I was able to open a page where I could name tracks before recording them but now in 9 I still haven't found out how to do this so land up with numbered tracks which I then rename in the bin.
As for track, channel, mixer naming...what a nightmare! I often land up having to rename almost everything twice per session and even then the mixer often displays something else! I'm almost at the point of having to just ignore names and go by region names and track numbers instead.
Create the amount of audio tracks you want and double click on their title (i.e. Audio 1, Audio 2 etc) on the arrangement layout or their title on the mixer layout and rename the track/s to what you want before you record.
If you forget to do this prior to recording and you name the tracks later, you can easily rename all the regions at once by selecting region > track names to regions
I would recommend setting up a template file with all your common recording tracks named so that you don't have to do this each time you start a project.

Project standards, naming conventions, colouring etc.

Hello everyone
I'm just starting using Logic, and after reading several posts on the benefits of good organisation (i.e. naming tracks, etc.) I'd like to know if there are any standard ways of naming tracks, projects and a colouring system that may have just developed in 'the industry'. I know many people will have their own way but often people tend to adopt what they've seen others do and this can become a kind of unofficial standard.
Since I'm starting from scratch, I want to adopt a standard way of:
Naming projects
Naming the Tracks
Colouring the tracks / mixer channels
(any other things to standardize?)
I'd rather start doing things in a way that would make it easier when sharing projects than just forge ahead my own way and end up looking back wishing I'd done it differently.
Hope this makes some sense?
Thanks.

Andy Scott3 wrote:
Maybe someone could help me out here.
In L7 I was able to open a page where I could name tracks before recording them but now in 9 I still haven't found out how to do this so land up with numbered tracks which I then rename in the bin.
As for track, channel, mixer naming...what a nightmare! I often land up having to rename almost everything twice per session and even then the mixer often displays something else! I'm almost at the point of having to just ignore names and go by region names and track numbers instead.
Create the amount of audio tracks you want and double click on their title (i.e. Audio 1, Audio 2 etc) on the arrangement layout or their title on the mixer layout and rename the track/s to what you want before you record.
If you forget to do this prior to recording and you name the tracks later, you can easily rename all the regions at once by selecting region > track names to regions
I would recommend setting up a template file with all your common recording tracks named so that you don't have to do this each time you start a project.

Naming Conventions for a BI Project

Hi Experts,
I am looking for some guidance on how to name my custom infoobjects, cubes, process chains, infopackages, sources etc.
What is the best approach and what naming convention to assign them?
Thanks,
Raj Jain

Hi Rajesh,
Naming conventions are always followed according to the customer standards... Some ask for Z* objects while others Y*.... If you have to find out how to name your objects.... go to your production system and search some custom objects... this might take some time but will save you the burden of rework.... Always please refer to your production systems for Naming conventions of any objects
Regards,
Pramod

Is it possible to control the naming convention used by Aperture when importing photos? If so, how

When I import photos from my camera, I have them placed into projects based on the date the photos were taken. However, I do not like the naming convention used by Aperture as it causes the projects to sort into a non-chronologial order. The convention is MMM-DD-YYYY and I want to change it to YYYY-MM-DD. Is it possible in Aperture 3.2.4 to do this?

In the Import panel you can edit the preset for the file name format to "Image year - image month - image day - index" for example; the preset for folder names seems to be gone in Aperture 3,3 - at least I cannot find it any longer. You only seem to be able to enter the folder name manually in the Import panel.

Class naming convention

many a times i face difficulty with the Action/Class naming convention.
Say, today ..i wrote a class.....tomorrow i have to rename the name of the class so that it becomes a more meaningful name and becomes unique and understandable with the newcomer classes.
...just to do this, i had to change the name of the class very frequently.
Though i follow few conventions like :
1) First letter of the class is Captial letter.
2) use names which is relevant with the classs's functionality.
but still i fall in problem....
say, i want to populate a DataBase with my class.....whats the name i should keep ? tommorrow i am going to write another class which also populate the database . what do i do ?
i first rename the old class with some meaningful name and then i write the new class with some other meaningful name.....but this kills time.....demands lots of changes....and so on...
you know, i get trouble when my number of classes increases.
do u feel the same ?
what are the rules (NOT JAVA RULES but meaningful rules) i should remember to keep a class name ?

You can name a class based on what it supposed to
do...
while naming it follow conventions like the ones
which are mentioned in the code
conventions/guidelines of your project.
You will not be writing the same functionality in two
different classes... would you??
In case you may need to refractor(rename the class
name) you may use java editor with refractoring
capability to do it..
With most of the java editors, you get this
functionality.. e.g. doing a Alt+Shift+R would
refractor your selected method, class, field etc...
This applies to Eclipse
>
Hope that helps..
Vaibhav

Data Modeler - Naming Conventions

I was using Oracle Designer for several year.
This product could drive you crazy because sometimes, but the strength was in my opinion the datamodelling part.
It saved you a lot of time because you kept stuck to the logical model generated your relational model and had all scripts satisfying all naming conventions you needed.
In Data Modeler i really miss the naming conventions and can't understand some parts, sometimes somebody here can help me if i have overseen something or it is just not implemented.
Naming conventions as example:
We work with surrogate keys.
Two well known tables - Employees (abbreviation EMP), Departments (abbreviation DEP)
They have one relation 1:N one department has many employees
In Designer i would define the EMPLOYEE entity, would set the table-abbreviation, the attributes and the primary key.
The same with DEPARTMENT. I would design it WITHOUT any column for the foreign key constraint.
Then i would create a relation between this two tables.
Last step is to generate the relational model.
a) Designer automatically adds ID as surrogate key on every table (you could configure that, it was dependent on a domain)
b) it automatically adds the table abbreviation as prefix on every column (even here it's configurable)
c) it automatically adds the a foreign key column in the child table with the prefix of the master table (f.e. EMP_DEP_ID or DEP_ID if you prefer not to prefix every column... what i do)
It was really easy to get your scripts.
Things i don't understand in Data Modeler:
In a logical model you should design entities, attributes and relations and don't mess around with FK-columns.
Is there any support for surrogate keys? I don't wanna add an ID manually with every table.
In Data Modeler an additional COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automatically. The name can just be changed in the Relational View afterward.
P.S.
Surrogate Keys.... There are some pros and cons for/against this out there. I have seen a lot of Oracle Projects and in all except one i always had a surrogate key column. It really makes life
easier. In the one no-surrogate-key-project we began to add surrogate keys after a while...

COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automaticallyLook at "General options>Naming Standard>templates" - you can define template for FK columns/attributes and then apply them for whole relational/logical model using "Apply Naming .." functionality from pop-up menu in the browser. For Logical model (FK attributes) - you also need to clear related setting at "General options>Logical>Keep as the name of originating attribute".
Templates are also used when objects are created, thus when new FK is created, then templates are used to generate name for foreign key and FK columns. Well you have to define table and column abbreviation in order to get them used in generated names - Re: Data Modeler: Naming
There is no support for surrogate keys in current release.
Philip

Purchase organization - naming convention

Hi,
Is there any best practice for the Purchase organization - naming convention in a global template project?
We have regional purchase organizations and country specific purchase organiozation in global template.
Regards,
AG

Thanks for your reply.
As the country specific purchasing organization will be linked to regional purchasing organization, should the naming convention of country specific purchasing organization, represents the first 2 digits of regional purchasing organization?

Project naming best practices

hi
the naming conventions for coding Java applications are clear to me. I'm wondering what the best practices are for naming Java projects e.g. when creating a new project in NetBeans IDE or in BitBucket?
thanks.

the naming conventions for coding Java applications are clear to me.
They are? What are they? Different orgs have their own naming standards. Other people have to be able to read, understand, maintain and enhance your code so standards are important.
I'm wondering what the best practices are for naming Java projects e.g. when creating a new project in NetBeans IDE or in BitBucket?
No one but your own business users and IT team even cares what you name your projects.

OWB Naming Conventions and Development Standards

Hi all,
I am developing a project in OWB. Could any one give me 'OWB Naming Conventions and Development Standards' document.

Hi,
You want to post this to the OWB forum:
Warehouse Builder
Thanks, Mark

Naming Conventions and Development Standards'

Hi all,
I am developing a project in OWB. Could any one give me 'OWB Naming Conventions and Development Standards' document.
Thanks

Hi,
You want to post this to the OWB forum:
Warehouse Builder
Thanks, Mark

Code Inspector - Naming conventions &mExtended Naming conventions for Progs

Hi experts,
I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
importing parameter : I[:type:]_
exporting parameter : E[:type:]_
changing parameter : C[:type:]_
tables parameter : T[:type:]_
but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
importing parameter : P_*
exporting parameter : P_*
changing parameter : P_*
tables parameter : P_*
I felt, while defining the function too, its better to have beginning with I_, E_, C_ or T_ instead of P_
is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
appreciate the opinions from experienced abap developers.
thanks,
Madhu_1980

Frank,
Thanks for your answer.
But what about Entity Objects, View Objects, View Links, and Application Modules.
I would like my developers to have an easy way to name them and also find them via intellisense.
So I was thinking in naming them the following way :
Entity Objects :
EO_Employee
EO_Department
View Objects :
VO_Employees
VO_Departments
View Links :
VL_EmployeesToDepartments
Application Module :
AM_HRService
However the use of "_" is not so "Java naming oriented".
So other alternatives would be:
1. take the "_" :
1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
2. Use the prefix at the end, but this way I loose the intellisense feature I want:
ex: EmployeeEO
Which naming approach are you using for big projects ?
Thanks,
Claudio.

[svn:fx-3.x] 12371: The main AccImpl was updated to handle accessible naming conventions differently than before .

Revision: 12371
Revision: 12371
Author:   [email protected]
Date:     2009-12-02 08:51:12 -0800 (Wed, 02 Dec 2009)
Log Message:
The main AccImpl was updated to handle accessible naming conventions differently than before. This change was made to make the 3.x branch consistent with the trunk changes. The updated methods allows the accessibilityName property to overwrite the logic that was previously used to build the accessible name for components that were inside of forms. This method also provides a method to allow developers to specificy that no form heading or form item label should be included in the accessibilityName for the form field by using a space.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as

Revision: 12371
Revision: 12371
Author:   [email protected]
Date:     2009-12-02 08:51:12 -0800 (Wed, 02 Dec 2009)
Log Message:
The main AccImpl was updated to handle accessible naming conventions differently than before. This change was made to make the 3.x branch consistent with the trunk changes. The updated methods allows the accessibilityName property to overwrite the logic that was previously used to build the accessible name for components that were inside of forms. This method also provides a method to allow developers to specificy that no form heading or form item label should be included in the accessibilityName for the form field by using a space.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as

Naming conventions in EP

Hi all,
we are currently in the process of preparing for Buisness Package certification in Enterprise Portal.
While going through the Test Plan provided by SAP describing the guidelines and the naming conventions.
Is there any thing that should be especially noted when we do the naming of EP folders and other EP components.Any help on these naming conventions is welcome.
Regards
Rohit.

Hi Rohit,
Please refer to the Vendor Structuring Guide (a.k.a. How to Certify Portal Content document) for more information on the naming conventions. You should have received this together with the test plan.
If you cannot locate this document, please contact your assigned integration consultant and/or complete and return the project registration document as much as you can so that the consultant can get back to you with any corrections that might be necessary.
Regards,
Mustafa.

Project Naming Conventions?

Similar Messages

Maybe you are looking for