Jing Tao

I verified even if we don't escape or encode the ampersand, we still get error. So I reopened this issue.

@mbjones @servilla @twhiteaker The feature to support `allowedNode` was implemented in Metacat and tested in the cn sandbox environment a while ago. It seems working on the sandbox env. However,...

@robyngit Two questions: 1. Does this feature only support the text data files (e.g, cvs)? How about Excel files? 2. What are the units of the range? Lines or bytes...

@mbjones Thanks! So I think we will use bytes for the range for any formats. The clients have the responsibility to parse the bytes.

Sure, Matt. On 11/27/21 2:20 PM, Matt Jones wrote: > > @taojing2002 jing, can you add this > to the next release please? > > — > You are receiving...

in the system meta schema, the format id is required: ``` ``` And `ObjectFormatIdentifier` should be a none-empty string: ``` A string used to identify an instance of :class:`Types.ObjectFormat` and...

In the mn.create/update and cn.create methods, the format id is checked.

@mbjones This is a request from Lauren. Here is an example of our member node document: https://knb.ecoinformatics.org/knb/d1/mn It has the base url of member node. But it doesn't have the...

@mbjones Sounds good. If I remember correctly, the properties starting with `CN` can NOT be added/overwritten to CN by the client through the register API, so we don't need to...

We are going to remove the identifier table on 3.0.0