Abstract
YesAbstract schemata are used for inheritance only and shouldn’t be used directly.
Interest
Since v0.6.8Inheritance
graph BT
Interest(Interest)
Interval(Interval)
click Interval "/explorer/schemata/Interval"
ContractAward(ContractAward)
click ContractAward "/explorer/schemata/ContractAward"
CourtCaseParty(CourtCaseParty)
click CourtCaseParty "/explorer/schemata/CourtCaseParty"
Directorship(Directorship)
click Directorship "/explorer/schemata/Directorship"
Documentation(Documentation)
click Documentation "/explorer/schemata/Documentation"
Employment(Employment)
click Employment "/explorer/schemata/Employment"
Membership(Membership)
click Membership "/explorer/schemata/Membership"
Ownership(Ownership)
click Ownership "/explorer/schemata/Ownership"
Post(Post)
click Post "/explorer/schemata/Post"
ProjectParticipant(ProjectParticipant)
click ProjectParticipant "/explorer/schemata/ProjectParticipant"
Representation(Representation)
click Representation "/explorer/schemata/Representation"
Succession(Succession)
click Succession "/explorer/schemata/Succession"
UnknownLink(UnknownLink)
click UnknownLink "/explorer/schemata/UnknownLink"
class Interest node-primary
Interest-->Interval
ContractAward-->Interest
CourtCaseParty-->Interest
Directorship-->Interest
Documentation-->Interest
Employment-->Interest
Membership-->Interest
Ownership-->Interest
Post-->Interest
ProjectParticipant-->Interest
Representation-->Interest
Succession-->Interest
UnknownLink-->Interest
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,
dateorstartDateshould be used as the temporal start.endDateshould be used as the temporal end. - Interest 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 |
Interest:role
|
Role | string |
Interval:sourceUrl
|
Source link | url |
Interval:startDate
|
Start date | date |
Interest:status
|
Status | string |
Interval:summary
|
Summary | text |