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.

Similar Messages

Adobe Interactive Forms - Standards & Naming Conventions

Does anyone know where I can locate any documentation pertaining to recommended standards and naming conventions for interactive forms within the SAP NetWeaver '04 platform?

Hi David,
I suggest you start here: https://www.sdn.sap.com/sdn/developerareas/was.sdn?page=AdobeForms.htm. This is where we have collected background information, demos, eLearning materials, and links to the standard documentation for the integrated forms solution. We work together with Adobe on the content of this site.
In due course, we will provide more tips & tricks and best practices.

BPC Standard Naming Convention

Hi Gurus,
Could you please share BPC naming conventions standards?
I am looking for prefix for objects such as:
Environment
Model
Dimension
Team
Task Profile
Data Access Profile
Member Formulas
Logic Script
Business Rule
Controls
Input Screen
Report
Data Manager Package
Data Manager Package Link
Transformation File
Conversion File
Process Chain
Thanks.

As far as I know there are no naming conventions other than no special characters or spaces. NW is case sensitive, so you need to be careful there. In terms of prefixes, I'm not sure what you mean. Some of the technical objects in NW are in the CPMB namespace but you are not adding that namespace to anything
Here are some comments:
Environment - the description in the BPC admin client can, the technical name on the backend will be generated
Model - same as environment
Dimension - same as environment
Member Formulas - this is driven by member IDs
Input Screen - not sure what this is
Data Manager Package
Process Chain - the out of the box PCs are all in the CPMB namespace, the new ones just need to be copied in there but they wouldn't be created in BPC rather in BW
Hope this make sense,
Akos

Standard Naming Conventions in XI

Hello,
Pls send pdfs/links for Naming Conventions in XI
Regards

Hi Henry,
These r the naming conventions to be followed in XI :
1) For Software Component, the naming convention should be :
   SAP_<SID>
where <SID> is the system ID if the applicable system
2) For Software Component Version, the naming convention should be :
    X.X
which shows the applicable version as of this date. Eg. SAP_ECC is at version 5.0
3) For Namespace the naming convention should be :
http://ERPGenie.COM/xi/<SCENARIO>/<SID>
where scenario refers to the interface being developed for and <SID> is the component where that object has relevance.
Eg. http://ERPGenie.COM/xi/OrderOutput/ECC will contain all the objects relevant to the Order Output scenario in the ECC system.
4) In Interface Objects ,
a) Message Interface should have the following naming convention :
MI_<meaningful name>_<IN/OUT/AB>
where:
IN = Inbound
OUT = Outbound
AB = Abstract (For BPM)
Remember to evaluate the IN and OUT based on the point of view from the source system to the target system. Eg. If we send an XML message from xEXTERNAL to an IDoc in ECC, then the XML Message is an OUT and the ECC is an IN interface.
b) Message Type should have the following naming convention :
MT_<meaningful name>
c) Fault Message Type should have the following naming convention :
FMT_<meaningful name>
d) Data Type should have the following naming convention :
DT_<meaningful name>
e) Data Type Enhancements should have the following naming convention :
DTE_<meaningful name>
f) Context Object should have the following naming convention :
CO_<meaningful name>
g) External Definition should have the following naming convention :
ED_<meaningful name>
5) In Mapping Objects,
a) Message Mapping should have the following naming convention :
MM_<meaningful name>_<source type>_<target type>
Eg. MM_ORDERSCENARIO_ORDERS05_OrderXML
b) Interface Mapping should have the following naming convention :
IM__<meaningful name>_<source type>_<target type>
Eg. IM_ORDERSCENARIO_ORDERS05_OrderXML
c) Mapping Templates should have the following naming convention :
MT__<meaningful name>_<source type>_<target type>
d) Imported Archives should have the following naming convention :
IA_<meaningful name>
6) In Services
a) Business Systems should have the following naming convention :
SAP<SID>
Where <SID> is the relevant system ID number
E.g.. SAPECC, SAPCRM, SAP46C
b) Business Services should have the following naming convention :
SRV_<XXXXXX>
Where XXXXXX is up to 6 characters to describe the type of service.
E.g. SRV_MAIL, SRV_FTP, SRV_SEEBRG
7) In Adapter Objects,
a) Adapter Meta Data should have the following naming convention :
AM_<meaningful name>
b) Communication Channel should have the following naming convention :
CC_<meaningful name>_<sender/receiver>
            E.g. CC_MAIL_SENDER
8) In Integration Objects,
a) Integration Process should have the following naming convention :
IP_<meaningful name> (Keep to 10 or less characters ALL CAPS)
            Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>
b) Actions should have the following naming convention :
<meaningful name>
Use Send_ or Receive_ to denote the sending or receiving of messages
Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>/<SID> where <SID> is system where the action is to be performed.
c) Integration Scenarios should have the following naming convention :
IS_<meaningful name> (Keep to 10 or less characters ALL CAPS)
The following web-sites may be helpful for complete naming standards in XI :
http://tsr.strain.at/space/SAP+XI(This web-site gives all detailed information about XI)
http://www.erpgenie.com/sap/netweaver/xi/namingconventions.htm
*********Please reward points if u find this useful.
cheers,
gyanaraj

Naming conventions included for linked files?

Perhaps a simple question but... if a file is only going to serve as a downloadable link (save as) do the standard naming conventions still apply? (lowercase, no spaces) the files i am working with are dwg, pdf, zmt, jpeg, png... my assumption is yes but thought i would ask.
thank you in advance,

All lowercase is nice, and easier since URLs are case-sensitive. Spaces are always best avoided. Completely. Some systems handle them, but there are no guarantees. Underscores (_) are a good alternative.

Naming conventions in XI !

Hi,
do we have any pdf or blog or links for the naming conventions to be followed in XI?
are there any standard naming conventions suggested or set by SAP for XI?
thank you,
regards,
Babu

Satish,
thank you for quick reply.
this link doesnt work;
http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm .
I have downloaded ASAP zip file from one of the link,if you think this is not useful then its fine otherwise can you give me the correct one.
thanks.
Babu

Change Existing objects naming conventions in a Query

Hi all,
I Need to change the Naming Conventions of the Query Objects of a Query at the Infoprovider level. Is there any Routine to change the naming conventions or do i need to do it Manually.

Hi gopinath,
mine is also a similar case, the problem with the option u gave me is that our implementation is in EDW environment and rework from the scratch is not an option for me. Is it possible to change the query objects naming convention at particular info-provider level, i have about 200 objects created with random naming convention and to be now changed according to a standard naming convention. I need to also consider how the changes effect other queries and reports as well.. So is there any possible way of Custom coding a routine or a program that can solve my purpose.. has any one gone through the same situation?
thanks,
kishore

Enterprise Object (EO) Naming Conventions for Controls

Post Author: rnagahori
CA Forum: Nsite
When naming controls you should follow standard naming conventions. Good names
describe the control, such as prodName, effectiveDate, and dateRequired. Avoid
special characters like "-" ," /", "<" , or ">" when naming your controls.

Post Author: rnagahori
CA Forum: Nsite
Additional notes ... Avoid using the following list of Reserved Variable Names:Application Builder uses several reserved variable names. Please do not use
these as the names of controls, or as variables within Action Builder
routines.
Reserved Names
sum
min
max
avg
abstract
boolean
break
byte
case
catch
char
class
const
continue
default
do
double
else
extends
false
final
finally
float
for
function
goto
if
implements
import
in
instanceof
int
interface
long
native
new
null
package
private
protected
public
return
short
static
super
switch
synchronized
this
throw
throws
transient
true
try
var
void
validate
while
with
_allowSubmitOnError
_fields
_form
_locked
_name
_queue.errorFields
_queue.errors
_queue.validation
_parent
_pointers
_showAlerts
_skipValidation
_status
obj
addEvent
addField
addMethod
addValidator
changedFields
checkForErrors
disabled
dump
forceValidation
hasChanged
getFields
optional
onSubmit
onValidate
removeField
required
reset
setFields
submit
submitCheck
description

Any document on naming conventions to be used in BPM?

Hi All,
Is there any document available which specifies the standard naming conventions to be used in BPM? Please respond, if there is any.
Regards.
Rajat

Hi,
you would need to put string constants in a file ending with .properties. From out of your application you replace all string constants with calls to a ResourceBundle class you'd have to instantiate for the .properties file.
ResourceBundles use a certain namin convention combining an arbitrary name with a locale such as _de for a german system for instance.
See the API docs at http://java.sun.com/j2se/1.4/docs/api/java/util/ResourceBundle.html
You can see an open source example of an application running in different locales at http://www.lightdev.com/dev/sh.htm
HTH
Ulrich

Naming conventions, corporate governance standards, etc.

We're beginning the process of setting up the Oracle portal in our company to support over 300 communities of practice as well as several other applications. Getting our corporate governance, naming standards, taxonomy usage guidelines, etc. outlined up front (and right!) will be critical to the success of the program. There seem to be infinite options within the portal product.
Have you developed standards, governance, guidelines, etc. for usage within your portal environment? What lessons did you learn along the way? What advice and recommendations would you give someone starting out to do the same?
Thanks.

Hi,
Did You get or made your own portelt and portlet parameter conventions?
If yes could you share it with me please?
At least the viewpoints, cornerstons of it?
Thanks.

Oracle BPEL standard, best practice and naming convention

Hi, folks,
Is there any standard or best practice associated with Oracle BPEL, regarding development, performace, what to avoid, etc? And is there any naming convention for the process, variable partner link name, etc? Similar to naming convention in writing Java code?
Thanks
John

Hi,
Here is the best practice guide:
http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf
Thanks & Regards,
Dharmendra
http://soa-howto.blogspot.com

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

Naming Conventions/Standards

Does anyone have any links to Best Practice documentation for Naming Standards or Conventions for physical data models e.g. naming of materialized views, indexes, tablespaces etc...

This topic has been discussed many times on various boards. Here is a thread from the comp.databases.oracle.server and .misc newsgroups. Also try searching here on this forum.
http://groups.google.com/group/comp.databases.oracle.server/browse_frm/thread/dfa2a3d3208a686f/30260cc08507f326?hl=en&lnk=st&q=#30260cc08507f326
HTH -- Mark D Powell --

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

Project standards, naming conventions, colouring etc.

Similar Messages

Maybe you are looking for