Feedback Community

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003" 

Lauren,

Those are not newly-created Communities, they've been around for quite some time.  It was I, not a member of SEMI Staff, who gave them their present names.  My goas is to get the Communities listed in the order in which we think of them, that is, "S3" coming before, for example "S10" and "S23".

If you look at the Discussion "Community Names and How They Are Sorted." in this Community, you'll find my concerns on this topic, including my advocacy of using three-digit numbers for SEMI Standards and Safety Guidelines:  "Also, as CONNECT sorts alphabetically, not alphanumerically, "23" precedes "3".  Therefore, I suggest we standardize on three-digit numbers (based on there being some letters of designators with more than 99 documents), using leading zeros to get CONNECT to sort Communities named for documents in the correct order.  For example, change "S1" to "S001", "S3" to "S003", and "S23" to "S023", so that they get listed in that order."

If having only one zero between the "S" and the single, non-zero digit of S1 through S9 (not all of which, AFAIK, have task forces currently) would offend you less, I'm happy to compromise at two-digit numbering for the "S" Documents, as I don't expect there to be more than 99 of them in my lifetime.

I point out that, if we settle on two-digit numbers, the "S23" TF won't have any leading zero.

Please let me know if you're comfortable compromising at two digits for the "S" documents.  If you are, I'll get rid of the extra zero in each of my TF's Community name.

TIA,
Eric

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003" 

While ordering is an nice goal I think natural reference is also very important. Perhaps we could consider the 4 leading digits an index and ensure it is followed immediately by the natural name, such as "S003 - SEMI S3 Heated Chemical Baths Task Force"  (or whatever the right descriptor is). 

Lauren,

Those are not newly-created Communities, they've been around for quite some time.  It was I, not a member of SEMI Staff, who gave them their present names.  My goas is to get the Communities listed in the order in which we think of them, that is, "S3" coming before, for example "S10" and "S23".

If you look at the Discussion "Community Names and How They Are Sorted." in this Community, you'll find my concerns on this topic, including my advocacy of using three-digit numbers for SEMI Standards and Safety Guidelines:  "Also, as CONNECT sorts alphabetically, not alphanumerically, "23" precedes "3".  Therefore, I suggest we standardize on three-digit numbers (based on there being some letters of designators with more than 99 documents), using leading zeros to get CONNECT to sort Communities named for documents in the correct order.  For example, change "S1" to "S001", "S3" to "S003", and "S23" to "S023", so that they get listed in that order."

If having only one zero between the "S" and the single, non-zero digit of S1 through S9 (not all of which, AFAIK, have task forces currently) would offend you less, I'm happy to compromise at two-digit numbering for the "S" Documents, as I don't expect there to be more than 99 of them in my lifetime.

I point out that, if we settle on two-digit numbers, the "S23" TF won't have any leading zero.

Please let me know if you're comfortable compromising at two digits for the "S" documents.  If you are, I'll get rid of the extra zero in each of my TF's Community name.

TIA,
Eric

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003" 

Lauren,

I propose to rename the 7 Communities that are affiliated with TFs I lead and that have names based on Document numbers thusly:

S001 Revision Task Force - North America -->
S01: SEMI S1 (safety labels) Revision Task Force - North America 

S002 Control of Hazardous Energy (CoHE) Task Force - North America  -->
S02:  SEMI S2 (semiconductor manufacturing equipment) Control of Hazardous Energy (CoHE) Task Force - North America  

S003 Revision Task Force - North America  -->
S03:  SEMI S3 (process chemical heating) Revision Task Force - North America  

S006 Revision Task Force - North America -->
S06: SEMI S6 (exhaust ventilation) Revision Task Force - North America 

S010 Revision Task Force - North America  -->
S10:  SEMI S10 (risk) Revision Task Force - North America  

S012 Task Force - North America  -->
S12:  SEMI S12 (equipment decontamination) Task Force - North America  

S030 (Energetic Materials EHS) Task Force - North America  -->
S30:  SEMI S30 (energetic materials) Task Force - North America  

The new names (if I haven't erred somewhere) get rid of the 'extra' leading zero, include 'SEMI' in the Document names (not something about which I care, but, IIRC, about which SEMI does care), and provide a brief reminder of the topic of each Document (I consider the Document titles to be too long to put in the Community names.).

For S23, I suggest:

S23 Global Task Force  -->
S23:  SEMI S23 (conservation of energy, utilities, and materials) Global Task Force

Eric

While ordering is an nice goal I think natural reference is also very important. Perhaps we could consider the 4 leading digits an index and ensure it is followed immediately by the natural name, such as "S003 - SEMI S3 Heated Chemical Baths Task Force"  (or whatever the right descriptor is). 

Lauren,

Those are not newly-created Communities, they've been around for quite some time.  It was I, not a member of SEMI Staff, who gave them their present names.  My goas is to get the Communities listed in the order in which we think of them, that is, "S3" coming before, for example "S10" and "S23".

If you look at the Discussion "Community Names and How They Are Sorted." in this Community, you'll find my concerns on this topic, including my advocacy of using three-digit numbers for SEMI Standards and Safety Guidelines:  "Also, as CONNECT sorts alphabetically, not alphanumerically, "23" precedes "3".  Therefore, I suggest we standardize on three-digit numbers (based on there being some letters of designators with more than 99 documents), using leading zeros to get CONNECT to sort Communities named for documents in the correct order.  For example, change "S1" to "S001", "S3" to "S003", and "S23" to "S023", so that they get listed in that order."

If having only one zero between the "S" and the single, non-zero digit of S1 through S9 (not all of which, AFAIK, have task forces currently) would offend you less, I'm happy to compromise at two-digit numbering for the "S" Documents, as I don't expect there to be more than 99 of them in my lifetime.

I point out that, if we settle on two-digit numbers, the "S23" TF won't have any leading zero.

Please let me know if you're comfortable compromising at two digits for the "S" documents.  If you are, I'll get rid of the extra zero in each of my TF's Community name.

TIA,
Eric

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003" 

Thanks, Eric. I agree with your proposal. 

Lauren,

I propose to rename the 7 Communities that are affiliated with TFs I lead and that have names based on Document numbers thusly:

S001 Revision Task Force - North America -->
S01: SEMI S1 (safety labels) Revision Task Force - North America 

S002 Control of Hazardous Energy (CoHE) Task Force - North America  -->
S02:  SEMI S2 (semiconductor manufacturing equipment) Control of Hazardous Energy (CoHE) Task Force - North America  

S003 Revision Task Force - North America  -->
S03:  SEMI S3 (process chemical heating) Revision Task Force - North America  

S006 Revision Task Force - North America -->
S06: SEMI S6 (exhaust ventilation) Revision Task Force - North America 

S010 Revision Task Force - North America  -->
S10:  SEMI S10 (risk) Revision Task Force - North America  

S012 Task Force - North America  -->
S12:  SEMI S12 (equipment decontamination) Task Force - North America  

S030 (Energetic Materials EHS) Task Force - North America  -->
S30:  SEMI S30 (energetic materials) Task Force - North America  

The new names (if I haven't erred somewhere) get rid of the 'extra' leading zero, include 'SEMI' in the Document names (not something about which I care, but, IIRC, about which SEMI does care), and provide a brief reminder of the topic of each Document (I consider the Document titles to be too long to put in the Community names.).

For S23, I suggest:

S23 Global Task Force  -->
S23:  SEMI S23 (conservation of energy, utilities, and materials) Global Task Force

Eric

While ordering is an nice goal I think natural reference is also very important. Perhaps we could consider the 4 leading digits an index and ensure it is followed immediately by the natural name, such as "S003 - SEMI S3 Heated Chemical Baths Task Force"  (or whatever the right descriptor is). 

Lauren,

Those are not newly-created Communities, they've been around for quite some time.  It was I, not a member of SEMI Staff, who gave them their present names.  My goas is to get the Communities listed in the order in which we think of them, that is, "S3" coming before, for example "S10" and "S23".

If you look at the Discussion "Community Names and How They Are Sorted." in this Community, you'll find my concerns on this topic, including my advocacy of using three-digit numbers for SEMI Standards and Safety Guidelines:  "Also, as CONNECT sorts alphabetically, not alphanumerically, "23" precedes "3".  Therefore, I suggest we standardize on three-digit numbers (based on there being some letters of designators with more than 99 documents), using leading zeros to get CONNECT to sort Communities named for documents in the correct order.  For example, change "S1" to "S001", "S3" to "S003", and "S23" to "S023", so that they get listed in that order."

If having only one zero between the "S" and the single, non-zero digit of S1 through S9 (not all of which, AFAIK, have task forces currently) would offend you less, I'm happy to compromise at two-digit numbering for the "S" Documents, as I don't expect there to be more than 99 of them in my lifetime.

I point out that, if we settle on two-digit numbers, the "S23" TF won't have any leading zero.

Please let me know if you're comfortable compromising at two digits for the "S" documents.  If you are, I'll get rid of the extra zero in each of my TF's Community name.

TIA,
Eric

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003" 

Lauren,

I've changed my seven.  I lack the necessary superpowers to change names of Communities affiliated with task forces I don't lead, so I can't change the S23 Community as we agreed..

You, however, should be able to change the S23 Community's name thusly:

1. In a list of Communities, click on the name of the S23 Community.
2. Click on 'Settings' button, to the right of the Community Name
3. Under 'Administration', click on 'Settings'
4. Replace/alter the contents of the 'Name*' field
5. In the row of buttons at the bottom of the screen (above the footer), click 'Save'.

'Almost painless'

Eric

Thanks, Eric. I agree with your proposal. 

Lauren,

I propose to rename the 7 Communities that are affiliated with TFs I lead and that have names based on Document numbers thusly:

S001 Revision Task Force - North America -->
S01: SEMI S1 (safety labels) Revision Task Force - North America 

S002 Control of Hazardous Energy (CoHE) Task Force - North America  -->
S02:  SEMI S2 (semiconductor manufacturing equipment) Control of Hazardous Energy (CoHE) Task Force - North America  

S003 Revision Task Force - North America  -->
S03:  SEMI S3 (process chemical heating) Revision Task Force - North America  

S006 Revision Task Force - North America -->
S06: SEMI S6 (exhaust ventilation) Revision Task Force - North America 

S010 Revision Task Force - North America  -->
S10:  SEMI S10 (risk) Revision Task Force - North America  

S012 Task Force - North America  -->
S12:  SEMI S12 (equipment decontamination) Task Force - North America  

S030 (Energetic Materials EHS) Task Force - North America  -->
S30:  SEMI S30 (energetic materials) Task Force - North America  

The new names (if I haven't erred somewhere) get rid of the 'extra' leading zero, include 'SEMI' in the Document names (not something about which I care, but, IIRC, about which SEMI does care), and provide a brief reminder of the topic of each Document (I consider the Document titles to be too long to put in the Community names.).

For S23, I suggest:

S23 Global Task Force  -->
S23:  SEMI S23 (conservation of energy, utilities, and materials) Global Task Force

Eric

While ordering is an nice goal I think natural reference is also very important. Perhaps we could consider the 4 leading digits an index and ensure it is followed immediately by the natural name, such as "S003 - SEMI S3 Heated Chemical Baths Task Force"  (or whatever the right descriptor is). 

Lauren,

Those are not newly-created Communities, they've been around for quite some time.  It was I, not a member of SEMI Staff, who gave them their present names.  My goas is to get the Communities listed in the order in which we think of them, that is, "S3" coming before, for example "S10" and "S23".

If you look at the Discussion "Community Names and How They Are Sorted." in this Community, you'll find my concerns on this topic, including my advocacy of using three-digit numbers for SEMI Standards and Safety Guidelines:  "Also, as CONNECT sorts alphabetically, not alphanumerically, "23" precedes "3".  Therefore, I suggest we standardize on three-digit numbers (based on there being some letters of designators with more than 99 documents), using leading zeros to get CONNECT to sort Communities named for documents in the correct order.  For example, change "S1" to "S001", "S3" to "S003", and "S23" to "S023", so that they get listed in that order."

If having only one zero between the "S" and the single, non-zero digit of S1 through S9 (not all of which, AFAIK, have task forces currently) would offend you less, I'm happy to compromise at two-digit numbering for the "S" Documents, as I don't expect there to be more than 99 of them in my lifetime.

I point out that, if we settle on two-digit numbers, the "S23" TF won't have any leading zero.

Please let me know if you're comfortable compromising at two digits for the "S" documents.  If you are, I'll get rid of the extra zero in each of my TF's Community name.

TIA,
Eric

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003" 

Lauren,

I've changed my seven.  I lack the necessary superpowers to change names of Communities affiliated with task forces I don't lead, so I can't change the S23 Community as we agreed..

You, however, should be able to change the S23 Community's name thusly:

1. In a list of Communities, click on the name of the S23 Community.
2. Click on 'Settings' button, to the right of the Community Name
3. Under 'Administration', click on 'Settings'
4. Replace/alter the contents of the 'Name*' field
5. In the row of buttons at the bottom of the screen (above the footer), click 'Save'.

'Almost painless'

Eric

Thanks, Eric. I agree with your proposal. 

Lauren,

I propose to rename the 7 Communities that are affiliated with TFs I lead and that have names based on Document numbers thusly:

S001 Revision Task Force - North America -->
S01: SEMI S1 (safety labels) Revision Task Force - North America 

S002 Control of Hazardous Energy (CoHE) Task Force - North America  -->
S02:  SEMI S2 (semiconductor manufacturing equipment) Control of Hazardous Energy (CoHE) Task Force - North America  

S003 Revision Task Force - North America  -->
S03:  SEMI S3 (process chemical heating) Revision Task Force - North America  

S006 Revision Task Force - North America -->
S06: SEMI S6 (exhaust ventilation) Revision Task Force - North America 

S010 Revision Task Force - North America  -->
S10:  SEMI S10 (risk) Revision Task Force - North America  

S012 Task Force - North America  -->
S12:  SEMI S12 (equipment decontamination) Task Force - North America  

S030 (Energetic Materials EHS) Task Force - North America  -->
S30:  SEMI S30 (energetic materials) Task Force - North America  

The new names (if I haven't erred somewhere) get rid of the 'extra' leading zero, include 'SEMI' in the Document names (not something about which I care, but, IIRC, about which SEMI does care), and provide a brief reminder of the topic of each Document (I consider the Document titles to be too long to put in the Community names.).

For S23, I suggest:

S23 Global Task Force  -->
S23:  SEMI S23 (conservation of energy, utilities, and materials) Global Task Force

Eric

While ordering is an nice goal I think natural reference is also very important. Perhaps we could consider the 4 leading digits an index and ensure it is followed immediately by the natural name, such as "S003 - SEMI S3 Heated Chemical Baths Task Force"  (or whatever the right descriptor is). 

Lauren,

Those are not newly-created Communities, they've been around for quite some time.  It was I, not a member of SEMI Staff, who gave them their present names.  My goas is to get the Communities listed in the order in which we think of them, that is, "S3" coming before, for example "S10" and "S23".

If you look at the Discussion "Community Names and How They Are Sorted." in this Community, you'll find my concerns on this topic, including my advocacy of using three-digit numbers for SEMI Standards and Safety Guidelines:  "Also, as CONNECT sorts alphabetically, not alphanumerically, "23" precedes "3".  Therefore, I suggest we standardize on three-digit numbers (based on there being some letters of designators with more than 99 documents), using leading zeros to get CONNECT to sort Communities named for documents in the correct order.  For example, change "S1" to "S001", "S3" to "S003", and "S23" to "S023", so that they get listed in that order."

If having only one zero between the "S" and the single, non-zero digit of S1 through S9 (not all of which, AFAIK, have task forces currently) would offend you less, I'm happy to compromise at two-digit numbering for the "S" Documents, as I don't expect there to be more than 99 of them in my lifetime.

I point out that, if we settle on two-digit numbers, the "S23" TF won't have any leading zero.

Please let me know if you're comfortable compromising at two digits for the "S" documents.  If you are, I'll get rid of the extra zero in each of my TF's Community name.

TIA,
Eric

Someone (SEMI???) has created several new communities with triple digit numerics such as "S002" and "S003". This is contrary to the common speech reference to those task forces, and indeed contrary to how SEMI refers to these task forces in events schedules. In other words, it should be "S3" not "S003"