在实体记录中标识id字段。
实体记录包含有效的ID。
如前所示，假定实体记录包括唯一的ID。
As indicated earlier, assume that an entity record includes a unique ID.
该接口使用了描述实体记录的模式和任何其他的参数。
The interface USES the schema describing the entity record and any other parameters.
区块的大小通常是实体记录大小的倍数。
The size of a block is typically a multiple of the size of a physical record.
直至永恒的实体记录；
当前的考虑是，模式的初始实现需要值类型始终等于实体记录。
The current thinking is that the pattern's initial implementation requires that the value type always equal the entity record.
要完成这项任务，需要有一项操作能够使用现有的ID来创建实体记录。
To do this, you need an operation to create an entity record with an existing ID.
作为查找操作的副作用，facade 将所有的实体记录添加到首选源。
The facade adds all the entity records to the preferred source as a side effect of the find operation.
为进行查找操作，facade仅返回实体记录，而不为写操作进行任何工作。
For find operations, the facade only returns the entity records and does nothing for write operations.
信息源可能有一个或者多个写操作，这些写操作允许客户端创建和更新实体记录。
The information source may have one or more write operations that allow a client to create and update entity records.
逻辑记录长度格式档案中每个逻辑与实体记录长度，以字节（即字段）为单位。
The length, in bytes (i. e. , columns ), of a logical and physical record in a logical record length formatted file.
因为客户端无法检测出id是无效的，所以它可以在另一个上下文中使用这个ID以链接实体记录。
Because the client can't detect that the id is invalid, it can use the id in another context to link to the entity record.
在迁移场景中，遗留源可能包含这样的实体记录，在企业的其他部分中引用了这些记录的ID。
In a migration scenario, legacy sources might contain entity records with IDs that are referenced in other parts of the enterprise.
这种机制（超出了这个模式范围）将周期性地运行，以删除那些不应该从备用源迁移到首选源的实体记录。
The mechanism (out of scope for this pattern) would run periodically to remove entity records that shouldn't be migrated from an alternate source to the preferred source.
当数个实体记录必须要包含某个特定变项，而这个变项并非定值的时候，就会使用标题记录。
Header records are often used when the number of physical records needed to contain the data for a particular variable is not constant for all variables.
而一个层级式档案可以用长方形档案结构储存，亦即所有的分析单位都存到单一笔的实体记录中。
A Hierarchical file can be stored in a rectangular file structure by storing all units of analysis in a single physical record.
所以当每笔数据或是每一分析单位被储存在一笔实体记录时这种档案结构就称为”逻辑记录长度”。
Thus, when the data for each case or unit of analysis is stored in a single physical record, the file structure is called "logical record length."
一个长方形档案中，每笔受访者的记录或是每个分析单位都包含相同的卡数或是相同的实体记录长度。
A rectangular file is one which contains the same number of card-images or the same physical record length for each respondent or unit of analysis.
为了让这种档案有一个相同的实体记录长度，短的逻辑记录会用空白填补，因此他们的实体记录长度相同。
In order to give such a file a common physical record length, short logical records are typically "padded" with blanks so that they will all be the same physical record length.
首选源模式假定一个信息源有一个或者多个查找操作，这些查找操作返回零个或多个实体记录的实例，或者可能是实体记录的一个子集。
The Preferred source Pattern assumes that an information source has one or more find operations that return zero or more instances of the entity record, or perhaps a subset of the entity record.
该模式假定从任何源所获得的信息都以描述实体的记录的形式出现，如客户或零部件。
The pattern assumes that information obtained from any source comes in the form of records that describe entities, such as customers or parts.
您还可以选择是显示单个记录还是一个列表，以及是否创建或者更改一个实体。
You can also select whether you want to display a single record or list and whether to create or update an entity.
此外，它还假定任何单独的实体都具有某个企业唯一的标识符，该标识符(例如，客户的编号或者sku)是记录的一部分。
Further, it assumes that any individual entity has some enterprise-unique identifier that's part of the record, such as a customer number or SKU.
某些数据元素或域本身或它们的组合对于理解整个记录或实体非常关键。
Certain data elements or domains either by themselves or in combination are critical to the understanding of an entire record or entity.
但是，在很多情况下，重要的实体是一个记录的一个子集，或者跨多个表，需要通过公共键链接数据。
However, in many cases, an entity of importance is a subset of a record, or spans several tables and requires data to be joined through a common key.
每个小卡片上记录了名称、职责和某些实体的合作者。
Each small card documents the name, responsibilities, and collaborators of some entity.
当将实体视为一个表时，不同的无重复记录的计数提供了基本的评估。
Where an entity is considered equal to a table, the count of distinct unduplicated records provides this basic assessment.
EIDB 中的 INSTANCES 表记录关于实例的信息，DE_INST表维护从每个文档实体到对应的实例的链接。
The INSTANCES table in the EIDB records information about instances, and the DE_INST table maintains the links from each document entity to the corresponding instance.
标识符中记录了请求实体的名字，这样如果有任何非法的使用，目标资源管理器就可以立即判断出来。
The identifiers have the requesting entity's name inscribed so that any illegal use could be immediately identified by the target resource managers.
应用推荐