IDRN Network Registry

PRO TIP: Take your raw data in the best shape you can get it, paste it into your favorite AI helper tool, and then tell it to format your data using the formatting data provided, and then cut-n-paste this formatting help information with that. Chances are good that it will create something useful.

The import file must be a CSV file. The first row must contain column names, and each row after that must contain one record to add or connect.

Required columns

type and name are required on every row.

• type: person, organization, org, location, geo, geographical, or sector.
• name: the person, organization, location, or sector name being added or updated.

Common optional columns

• target: the person, organization, location, or sector connected to this row.
• target_type: person, organization, location, or sector for the target.
• relationship_type: Personal, Organizational, Geographical, or Service Sector.
• strength: whole number from -4 to +4. Blank strength uses the Default strength slider and marks the relationship for confirmation.
• subject: the person or record the relationship is on behalf of. If blank, the row name is used.
• subject_type: person, organization, location, or sector. If blank, person is assumed.
• sector: optional IDRN sector tag, such as N, F, L, M, or X.
• note: a short note added to the relationship.

Accepted alternate column names

The importer recognizes several friendly header names. For example, node_name or entity_name can be used instead of name; connected_to, connection_name, or entity can be used instead of target; weight can be used instead of strength.

Dataset organization

The Dataset organization field in the Import Data menu connects every imported person to one shared organization. This is useful when importing a roster from one group, event, partner list, or organization.

Dataset relationship note

The Dataset relationship note is applied to every imported relationship. If you enter one, it overrides row-by-row notes for the imported relationships.

Example: simple people connected to an organization

type,name,target,target_type,relationship_type,strength,note
person,Paula Wallace,IDRN Global,organization,Organizational,2,Added from partner roster
person,Steve Newton,IDRN Global,organization,Organizational,3,Active response contact
person,Liz Aldita,Indonesia,location,Geographical,1,Regional contact

Example: using subject for relationships on behalf of someone else

type,name,subject,subject_type,target,target_type,relationship_type,strength,note
person,Miriam Wallace,Miriam Wallace,person,Paula Wallace,person,Personal,2,Family relationship
organization,IDRN Global,Miriam Wallace,person,Big Life,organization,Organizational,3,Introduced by Miriam

Example: node-only rows

If a row has no target, the importer creates or updates the node but does not create a relationship.

type,name,sector,note
organization,New Partner Network,N,Created as a standalone organization
person,Jordan Smith,X,Created as a standalone person

Example: connection_data shortcut

You may place relationship details in one connection_data field. Use this only when a source file already stores connection details in one column.

type,name,connection_data
person,Ana Lopez,"target=IDRN Global; target_type=organization; relationship_type=Organizational; strength=2; note=Imported relationship"

Important notes

• Use one row per record or relationship.
• Names should be spelled consistently to avoid accidental duplicates.
• Blank strength values are allowed, but they will be marked as needing confirmation.
• Imports update matching relationships instead of creating duplicates when the same source, target, and relationship type already exist.
• Always review the preview before clicking Import previewed rows.