Abstract
YesAbstract schemata are used for inheritance only and shouldn’t be used directly.
Interval
Since v0.6.8An object which is bounded in time.
Inheritance
graph BT
Interval(Interval)
Associate(Associate)
click Associate "/explorer/schemata/Associate"
Call(Call)
click Call "/explorer/schemata/Call"
CallForTenders(CallForTenders)
click CallForTenders "/explorer/schemata/CallForTenders"
Debt(Debt)
click Debt "/explorer/schemata/Debt"
EconomicActivity(EconomicActivity)
click EconomicActivity "/explorer/schemata/EconomicActivity"
Event(Event)
click Event "/explorer/schemata/Event"
Family(Family)
click Family "/explorer/schemata/Family"
Identification(Identification)
click Identification "/explorer/schemata/Identification"
Interest(Interest)
click Interest "/explorer/schemata/Interest"
Message(Message)
click Message "/explorer/schemata/Message"
Occupancy(Occupancy)
click Occupancy "/explorer/schemata/Occupancy"
Payment(Payment)
click Payment "/explorer/schemata/Payment"
Project(Project)
click Project "/explorer/schemata/Project"
Sanction(Sanction)
click Sanction "/explorer/schemata/Sanction"
TaxRoll(TaxRoll)
click TaxRoll "/explorer/schemata/TaxRoll"
class Interval node-primary
Associate-->Interval
Call-->Interval
CallForTenders-->Interval
Debt-->Interval
EconomicActivity-->Interval
Event-->Interval
Family-->Interval
Identification-->Interval
Interest-->Interval
Message-->Interval
Occupancy-->Interval
Payment-->Interval
Project-->Interval
Sanction-->Interval
TaxRoll-->Interval
Info
Generated
NoEntities using a generated schema shouldn’t be created directly by users.
Matchable
NoEntities using a matchable schema can be used for matching and cross-referencing.
Hidden
NoEntities using a hidden schema shouldn’t be displayed in user interfaces or created by users.
Semantics
FollowTheMoney has well-defined semantics for different representations of entities, for example in a network graph or in a timeline.
- In a network graph, entities should be represented as a vertex.
-
In a timeline,
startDateordateshould be used as the temporal start.endDateshould be used as the temporal end. - Interval entities have no temporal extent, i.e. they are not suitable for representation in a timeline.
Properties
| Name | Label | Type |
|---|---|---|
Interval:alephUrl | Aleph URL | url |
Interval:date | Date | date |
Interval:description | Description | text |
Interval:endDate | End date | date |
Interval:indexText | Index text | text |
Interval:modifiedAt | Modified on | date |
Interval:namesMentioned | Detected names | name |
Interval:publisher | Publishing source | string |
Interval:publisherUrl | Publishing source URL | url |
Interval:recordId | Record ID | string |
Interval:retrievedAt | Retrieved on | date |
Interval:sourceUrl | Source link | url |
Interval:startDate | Start date | date |
Interval:summary | Summary | text |