Implicating cephalopod → mollusk
Link to implication

Reason:

Cephalopoda is a mollusk class.

Related implications:

• gastropod → mollusk.
• nudibranch → sea_slug.
• sea_angel → sea_slug.
• sea_slug → marine.

• bivalve → mollusk.
• bivalve → marine.
• scallop → bivalve.
• oyster → bivalve.
• clam → bivalve.
• geoduck → clam.

Related aliases:

• mollusc → mollusk.
• shellfish → shellfish_(disambiguation)¹.

¹ "Shellfish" may refer to almost any aquatic invertebrate that have visible shell or exoskeleton.

For more information see forum #213618.

O16 said:

• clam → mollusk.
• clam → marine

Are there any non-marine mollusks? If not, then implicating clam → mollusk and mollusk → marine would seem to fit better

phantomreader42 said:
Are there any non-marine mollusks?

post #449793

O16 said:

Related implications:

• clam → mollusk.

Related aliases:

• clam → bivalve¹.

Either the top one needs clam changed to bivalve to the bottom one needs to be flipped. You should never implicate and alias the same tag.

BlueDingo said:
Either the top one needs clam changed to bivalve to the bottom one needs to be flipped. You should never implicate and alias the same tag.

Sorry, but I can't see where exactly is the problem.
With the alias clam → bivalve, either implications (clam → mollusk or bivalve → mollusk) wuold have the same efect: if someone tag a post with "clam" the resulting tags would be "bivalve" and "mollusk".

O16 said:
Sorry, but I can't see where exactly is the problem.
With the alias clam → bivalve, either implications (clam → mollusk or bivalve → mollusk) wuold have the same efect: if someone tag a post with "clam" the resulting tags would be "bivalve" and "mollusk".

If the alias happens first, clam A-> bivalve will change clam to bivalve but then clam I-> mollusk won't take place because clam is no longer in the list. And what if someone tags bivalve instead of clam? Same problem, no clam to implicate.

Remember that computing operations are never simultaneous. One must happen before the other and you should always try to avoid the possibility of something going wrong.

BlueDingo said:
If the alias happens first, clam A-> bivalve will change clam to bivalve but then clam I-> mollusk won't take place because clam is no longer in the list. And what if someone tags bivalve instead of clam? Same problem, no clam to implicate.

Remember that computing operations are never simultaneous. One must happen before the other and you should always try to avoid the possibility of something going wrong.

Thank you for this information. The proper changes will be made.

I am bumping this, the reason is to state some changes in the suggestions. Some species have been added, but the most important change is that the original request for aliasing 'clam' to 'bivalve' was changed to an implication request.

Explanation :

The term 'clam' can be used to basically any bivalve, but it is mostly directed to the conjunct of species with smooth shells which usually dig in sand or mud. Due to this I landed to the conclusion that would be better to adapt the tag according this usage and implicate it instead of aliasing.