Equipment naming collisions - anticipated issue

[CBroz1]

Across a number of element workflows, we specify an equipment or device table in the pipeline.

• workflow-calcium-imaging Equipment with scanner
• workflow-facemap Device with recorder_id
• workflow-deeplabcut Device with camera_id

Currently, I think facemap and deeplabcut can be used simultaneously, but I propose we adopt a naming convention within workflows so that all elements work together smoothly out of the box (e.g., FacemapEquipment, DeepLabCutEquipment). A user could collapse these tables

[CBroz1]

The team discussed changing this table to Device to minimize disruptions to existing pipelines

• workflow-calcium-imaging
• workflow-deeplabcut
• workflow-facemap
• workflow-miniscope

@lab.schema
class Device(dj.Manual):
    definition = """
    device.                 : varchar(32)
    ---
    modality               : varchar(64)
    description=null  : varchar(256)
    """

[CBroz1]

Updated above to reflect discussion

[CBroz1]

In discussion between @ttngu207 and @kabilar, the team decided not to standardize workflow-level namespaces